View PM5361-RI_2043130.PDF datasheet online --- IC-ON-LINE

Datasheet File OCR Text:

pm5361 tupp data sheet pmc-920526 issue 8 tributary unit payload processor proprietary and confidential to pmc-sierra, inc., and for its customers internal use pm5361 tupp sonet/sdh tributary unit payload processor data sheet issue 8: july 1998
pm5361 tupp data sheet pmc-920526 issue 8 tributary unit payload processor proprietary and confidential to pmc-sierra, inc., and for its customers internal use public revision history issue no. issue date details of change 8 july 1998 data sheet reformatted no change in technical content. generated r8 data sheet from pmc- 920102, issue r10.
pm5361 tupp data sheet pmc-920526 issue 8 tributary unit payload processor proprietary and confidential to pmc-sierra, inc., and for its customers internal use i contents 1 features ...................................................................................................................... ................1 2 applications .................................................................................................................. .............3 3 references .................................................................................................................... ............4 4 application example........................................................................................................... .....5 5 block diagram ................................................................................................................. ..........6 6 description ................................................................................................................... .............8 7 pin diagram ................................................................................................................... ............10 8 pin description ............................................................................................................... ........11 9 functional description ......................................................................................................22 9.1 input bus demultiplexer .....................................................................22 9.2 output bus multiplexer ......................................................................22 9.3 tributary payload processor ..........................................................23 9.3.1 clock generator.....................................................................23 9.3.2 incoming timing generator..................................................23 9.3.3 incoming multiframe detector..........................................24 9.3.4 pointer interpreter ..............................................................24 9.3.5 payload buffer .........................................................................24 9.3.6 outgoing timing generator ................................................25 9.3.7 pointer generator.................................................................25 9.3.8 common bus interface ..........................................................26 9.4 microprocessor interface ...............................................................26 9.5 register memory map...........................................................................26
pm5361 tupp data sheet pmc-920526 issue 8 tributary unit payload processor proprietary and confidential to pmc-sierra, inc., and for its customers internal use ii 10 normal mode register description ...............................................................................29 11 test features description ................................................................................................64 11.1 i/o test mode ............................................................................................67 12 operation .................................................................................................................... ..............68 12.1 configuration options ........................................................................68 12.2 sts-1 mode.................................................................................................70 12.3 au3 mode ....................................................................................................70 12.4 au4 mode ....................................................................................................71 13 functional timing ............................................................................................................ ......74 14 absolute maximum ratings .................................................................................................82 15 d.c. characteristics ......................................................................................................... ....83 16 microprocessor interface timing characteristics ...............................................85 17 tupp timing characteristics .............................................................................................92 18 ordering and thermal information ...............................................................................96 19 mechanical information......................................................................................................9 7
pm5361 tupp data sheet pmc-920526 issue 8 tributary unit payload processor proprietary and confidential to pmc-sierra, inc., and for its customers internal use iii list of registers register 00h: master incoming configuration.........................................................................30 register 01h: master outgoing configuration........................................................................32 register 02h: input signal activity monitor..............................................................................34 register 03h: master reset and identity....................................................................................36 register 04h: tributary payload processor #1 configuration ..........................................37 register 05h: tributary payload processor #2 configuration ..........................................39 register 06h: tributary payload processor #3 configuration ..........................................41 register 07h: tpp and h4 oof interrupt enable .......................................................................43 register 08h: tpp interrupt status and h4 oof status ..........................................................45 register 09h: parity error and h4 oof interrupt ...................................................................47 register 20h, 40h, 60h: tu3, or tu #1 in tug2 #1, configuration and status......................49 register 21h-26h, 41h-46h, 61h-66h: tu #1 in tug2 #2 to tug2 #7, configuration and status 51 register 27h, 47h, 67h: tu3 or tu #1 in tug2 #1 to tug2 #7, lop interrupt .........................53 register 28h-2eh, 48h-4eh, 68h-6eh: tu #2 in tug2 #1 to tug2 #7, configuration and status 55 register 2fh, 4fh, 6fh: tu #2 in tug2 #1 to tug2 #7 .....................................................................57 register 30h-36h, 50h-56h, 70h-76h: tu #3 in tug2 #1 to tug2 #7, configuration and status 58 register 37h, 57h, 77h: tu #3 in tug2 #1 to tug2 #7, lop interrupt .......................................60 register 38h-3eh, 58h-5eh, 78h-7eh: tu #4 in tug2 #2 to tug2 #7, configuration and status 61 register 3fh, 5fh, 7fh: tu #4 in tug2 #1 to tug2 #7, lop interrupt.......................................63 register 80h: master test ...................................................................................................... ..........66
pm5361 tupp data sheet pmc-920526 issue 8 tributary unit payload processor proprietary and confidential to pmc-sierra, inc., and for its customers internal use iv list of figures figure 1 - sonet/sdh tributary cross-connect application ..........................................5 figure 2 - overall device ....................................................................................................... ......6 figure 3 - each tributary payload processor .....................................................................7 figure 4 - sonet sts-3 carrying vt1.5 within sts-1 ...........................................................70 figure 5 - sdh stm-1 carrying tu12 within vc3/au3 ............................................................71 figure 6 - sdh stm-1 carrying tu12 within tug3/au4..........................................................71 figure 7 - sdh stm-1 carrying tu3 within tug3 ...................................................................72 figure 8 - sdh stm-1 carrying mix of tu11, tu12, tu3 within tug3/au4 .........................73 figure 9 - input bus timing - simple sts-1/au3 case ...........................................................74 figure 10 - input bus timing - complex sts-1 / au3 case .....................................................75 figure 11 - input bus timing - au4 case.....................................................................................76 figure 12 - output bus timing - locked sts-1 spes / au3 vcs case .................................77 figure 13 - output bus timing - floating sts-1 spes / au3 vcs case...............................78 figure 14 - output bus timing - locked au4 vc case ...........................................................79 figure 15 - output bus timing - floating au4 vc case.........................................................80 figure 16 - by-passed mode functional timing .....................................................................81 figure 17 - microprocessor interface read timing (intel mode) .................................86 figure 18 - microprocessor interface read timing (motorola mode) .......................87 figure 19 - microprocessor interface write timing (intel mode)................................89 figure 20 - microprocessor interface write timing (motorola mode)......................90 figure 21 - input timing........................................................................................................ ..........93 figure 22 - output timing....................................................................................................... .......94
pm5361 tupp data sheet pmc-920526 issue 8 tributary unit payload processor proprietary and confidential to pmc-sierra, inc., and for its customers internal use v list of tables table 1 - test mode register memory map ........................................................................64 table 2 - i/o test mode input read register description .......................................67 table 3 - i/o test mode output write register description ..................................67 table 4 - d.c. characteristics ................................................................................................83 table 5 - microprocessor interface read access (figure 17, figure 18)..............85 table 6 - microprocessor interface write access (figure 19, figure 20) ............88 table 7 - tupp input (figure 21)...............................................................................................9 2 table 8 - tupp output (figure 22)...........................................................................................94 table 9 - tupp ordering information...................................................................................96 table 10 - tupp thermal information .....................................................................................96
pm5361 tupp data sheet pmc-920526 issue 8 tributary unit payload processor proprietary and confidential to pmc-sierra, inc., and for its customers internal use vi
pm5361 tupp data sheet pmc-920526 issue 8 tributary unit payload processor proprietary and confidential to pmc-sierra, inc., and for its customers internal use 1 1 features configurable, multi-channel, payload processor for alignment of sonet virtual tributaries (vts) or sdh tributary units (tus). processes an sts-3 or stm-1 byte serial data stream. transfers all incoming tributaries in the three sts-1 synchronous payload envelopes of an sts-3 byte serial stream to the three sts-1 synchronous payload envelopes of an outgoing sts-3 byte serial stream. transfers all incoming tributaries in the single au4 or three au3 administrative units of an stm-1 byte serial stream to the single au4 or three au3 administrative units of an outgoing stm-1 byte serial stream. compensates for pleisiochronous relationships between incoming and outgoing higher level (sts-1, au4, au3) synchronous payload envelope frame rates through processing of the lower level (vt6, vt3, vt2, vt1.5, tu3, tu2, tu12, or tu11) tributary pointers. provides multiframe synchronization for ring closure at the headend node in a sonet/sdh ring. provides independently configurable au3/au4 frame format on incoming and outgoing directions. configurable to process any legal mix of tributaries such as vt1.5, vt2, vt3, vt6, tu11, tu12, tu2, or tu3. each vt group or tug2 can be configured to carry one of four tributary types. tug2s can be multiplexed into vc3s or tug3s. each tug3 can also be configured to carry a tu3. optionally frames to the h4 byte in the path overhead to determine tributary multiframe boundaries. internally generated h4 bytes with leading logic 1 bits are inserted into the outgoing administrative units. verifies parity on the ic1j1 and ispe signals and on the incoming data stream and generates parity on the outgoing data stream. detects loss of pointer and re-acquisition for each tributary and optionally generates interrupts. loss of pointer detection can optionally generate tributary path ais.
pm5361 tupp data sheet pmc-920526 issue 8 tributary unit payload processor proprietary and confidential to pmc-sierra, inc., and for its customers internal use 2 allows insertion of all zeros or all ones tributary idle code with unequipped indication and valid pointer into any tributary. allows insertion of tributary path ais into any tributary. operates in conjunction with the pm5323 tspp triple sonet/sdh payload processor and the pm5344 sonet/sdh path terminating transceiver to align tributaries such that they can be switched by the pm5371 tudx sonet/sdh tributary unit cross-connect. operates from a single 19.44 mhz clock. provides a generic 8-bit microprocessor bus interface for configuration, control, and status monitoring. low power, +5 volt, cmos technology, ttl compatible inputs and outputs. 160 pin plastic quad flat pack (pqfp) package
pm5361 tupp data sheet pmc-920526 issue 8 tributary unit payload processor proprietary and confidential to pmc-sierra, inc., and for its customers internal use 3 2 applications sonet and sdh wideband cross-connects sonet and sdh add-drop and terminal multiplexers
pm5361 tupp data sheet pmc-920526 issue 8 tributary unit payload processor proprietary and confidential to pmc-sierra, inc., and for its customers internal use 4 3 references 1. american national standard for telecommunications - digital hierarchy - optical interface rates and formats specification, ansi t1.105-1988. 2. ccitt blue book, recommendation g.708 - "network node interface for the synchronous digital hierarchy", volume iii, fascicle iii.4, 1988. 3. ccitt blue book, recommendation g.709 - "synchronous multiplexing structure", volume iii, fascicle iii.4, 1988. 4. ccitt study group xviii, report r 33 - "recommendations drafted by working party xviii/7" (digital hierarchies) to be approved in 1990 including revised draft recommendations g.708 and g.709", june 1990. 5. bell communications research - sonet transport systems: common generic criteria, tr-tsy-000253, issue 2, december 1991.
pm5361 tupp data sheet pmc-920526 issue 8 tributary unit payload processor proprietary and confidential to pmc-sierra, inc., and for its customers internal use 5 4 application example the pm5361 tupp is typically used as part of a sonet/sdh tributary cross- connect. tupps can be used to transfer the payloads of incoming tributaries into outgoing tributaries that are aligned to facilitate switching. a typical example is shown below. this example shows the tributaries extracted from an sts-1 or au3 path terminating device, such as the pm5344 sptx sonet/sdh path terminating transceiver, being routed through tupps so as to be aligned for cross- connection using the pm5371 tudx sonet/sdh tributary unit cross-connect. the tupp (and sptx) can be bypassed by switching through whole sts-1s or au3s that are output by the pm5323 tspp triple sonet/sdh payload processor. note that in this application example, the tupps are operating in locked output mode (i.e. their oj1en bits are low) to allow convenient interfacing to the tudx chip. figure 1 - sonet/sdh tributary cross-connect application pm5361 tupp ispe ospe itmf dout/opar otspe ic1j1 sclk oc1j1 otmf otv5 sinl doutl dinl soutl ofseb dinr soutr odeb sfp sclk ofp ifp sinr doutr from pm5344 sptx #2 from pm5344 sptx #1 from pm5344 sptx #1 from pm5344 sptx #2 to pm5344 sptx #2 to pm5344 sptx #1 din/ipar ispe ospe itmf dout/opar otspe ic1j1 sclk oc1j1 otmf otv5 din/ipar sobeb aobeb pm5371 tudx pm5361 tupp
pm5361 tupp data sheet pmc-920526 issue 8 tributary unit payload processor proprietary and confidential to pmc-sierra, inc., and for its customers internal use 6 5 block diagram figure 2 - overall device rstb csb rdb wrb ale a[7:0] mbeb d[7:0] din[7:0] sclk ic1j1 tributary payload processor input demux micro- processor interface ispe tributary payload processor tributary payload processor output mux dout[7:0] otmf oc1j1 ospe otspe otv5 intb itmf ipar opar
pm5361 tupp data sheet pmc-920526 issue 8 tributary unit payload processor proprietary and confidential to pmc-sierra, inc., and for its customers internal use 7 figure 3 - each tributary payload processor otv5 otspe din[7:0] ospe pointer interpreter rstb tstb bsb rdb wrb trsb a[4:0] d[7:0] common bus interface payload buffer pointer generator incoming timing generator outgoing timing generator incoming multiframe detector clock generator ic1j1 ispe sclk to all blocks ioclk dtmf dout[7:0] oc1j1 otmf int nofilt itug3 itmf tu3 otug3 trig oof icode1 icode
pm5361 tupp data sheet pmc-920526 issue 8 tributary unit payload processor proprietary and confidential to pmc-sierra, inc., and for its customers internal use 8 6 description the pm5361 tupp sonet/sdh tributary unit payload processor is a monolithic integrated circuit that implements a configurable, multi-channel, payload processor for alignment of sonet virtual tributaries (vts) or sdh tributary units (tus.) when configured for sonet compatible operation, the tupp transfers all tributaries in the three sts-1 synchronous payload envelopes of an incoming sts-3 byte serial stream to the three sts-1 synchronous payload envelopes of an outgoing sts-3 byte serial stream. similarly, when configured for sdh compatible operation, the tupp transfers all tributaries in the single au4 or three au3 administrative units of an incoming stm-1 byte serial stream to a single au4 or three au3 administrative units of an outgoing stm-1 byte serial stream. the tupp compensates for pleisiochronous relationships between incoming and outgoing higher level (sts-1, au4, au3) synchronous payload envelope frame rates through processing of the lower level (vt6, vt3, vt2, vt1.5, tu3, tu2, tu12, tu11) tributary pointers. the tupp is configurable to process any legal mix of tributaries. each vt group can be configured to carry any one of the four tributary types (vt1.5, vt2, vt3, or vt6) and each tug2 can be configured to carry any one of three tributary types (tu11, tu12, or tu2). tug2s can be multiplexed into a vc3 or a tug3. alternatively, each tug3 can be configured to carry a tu3. the tupp operates in conjunction with the pm5323 tspp triple sonet/sdh payload processor and the pm5344 sonet/sdh path terminating transceiver to align tributaries such that they can be switched by the pm5371 tudx sonet/sdh tributary unit cross-connect. the tupp provides useful maintenance functions. they include detection of loss of pointer and pointer re-acquisition for each tributary, and optional generation of interrupts. the tupp also allows insertion of tributary path ais or tributary idle (unequipped). the tupp can also insert inverted new data flag fields that can be used to diagnose downstream pointer processing elements. no auxiliary high speed clocks are required as the tupp operates from a single 19.44 mhz line rate clock. the tupp is configured, controlled and monitored via a generic 8-bit microprocessor bus interface.
pm5361 tupp data sheet pmc-920526 issue 8 tributary unit payload processor proprietary and confidential to pmc-sierra, inc., and for its customers internal use 9 the tupp is implemented in low power, +5 volt, cmos technology. it has ttl compatible inputs and outputs and is packaged in a 160 pin pqfp package.
pm5361 tupp data sheet pmc-920526 issue 8 tributary unit payload processor proprietary and confidential to pmc-sierra, inc., and for its customers internal use 10 7 pin diagram the tupp is packaged in an 160 pin pqfp package having a body size of 28 mm by 28 mm and a pin pitch of 0.65 mm. pm5361 tupp vsst nc ale nc rdb/e nc wrb/rwb vsst vsst nc otv5 nc otspe nc ospe vddi nc nc vsst vsst vsst nc nc vddi vddo sclk vsso vssi nc nc nc vsst vsst vsst vsst nc nc dnc (odv) nc vddo vsso nc dout[0] nc dout[1] nc opar vsst vsst vsst a[0] a[1] a[2] a[3] a[4] a[5] a[6] a[7] (a[8]) dnc csb mbeb vsst nc din[0] nc itmf nc vssi nc ispe nc vddi vsst vsst vsst nc nc nc nc dout[2] d[0] d[1] d[2] d[3] din[1] nc din[2] nc dout[3] nc nc ic1j1 nc nc nc vsso vddo vddi vssi vsso d[4] nc vddo vddi vssi vsso nc din[3] nc din[4] nc d[5] d[6] d[7] nc intb vsso nc dout[4] din[5] nc din[6] nc din[7] nc ipar nc nc dout[5] nc dout[6] nc dout[7] nc vddo vsso vssi oc1j1 nc otmf nc vsst vsst rstb vsst nc vddo vsso nc dnc (imfa) vsst vsst vddi nc vssi nc nc nc vsst vsst pin 1 pin 160 pin 121 pin 120 pin 40 pin 41 pin 80 index pin 81 (top view)
pm5361 tupp data sheet pmc-920526 issue 8 tributary unit payload processor proprietary and confidential to pmc-sierra, inc., and for its customers internal use 11 8 pin description pin name type pin no. function sclk input 153 the system clock (sclk) provides timing for tupp internal operation. sclk is a 19.44 mhz, nominally 50% duty cycle clock. vclk the test vector clock (vclk) signal is used during tupp production testing to verify internal functionality. ic1j1 input 44 the input c1/j1 frame pulse (ic1j1) identifies the transport envelope and synchronous payload envelope frame boundaries on the din[7:0] bus. ic1j1 is set high while ispe is low to mark the first c1 byte of the transport envelope frame on the din[7:0] bus. ic1j1 is set high while ispe is high to mark each of the j1 bytes of the synchronous payload envelope(s) on the din[7:0] bus. ic1j1 must be present at every occurrence of the first c1 and all j1 bytes. the tupp will ignore a pulse on ic1j1 at the byte position of the v1 byte of the first tributary of each tug3 or vc3. ic1j1 is sampled on the rising edge of sclk.
pm5361 tupp data sheet pmc-920526 issue 8 tributary unit payload processor proprietary and confidential to pmc-sierra, inc., and for its customers internal use 12 pin name type pin no. function itmf input 52 the active high incoming tributary multiframe (itmf) signal identifies the first frame of the tributary multiframe for each sts-1 synchronous payload envelope, au3, or au4 administrative unit. itmf is enabled by the setting the itmfen register bit high. when itmfen bit is low, the path overhead h4 byte is used to determine tributary multiframe boundaries. itmf is selectable to pulse high during the v1 byte of the first tributary or during the h4 byte which indicates that the next frame is the first frame of the tributary multiframe. selection between marking v1 or h4 bytes is controlled by the itmfh4 register bit. pulses on itmf are only effective during the h4 or v1 byte positions, as appropriate. itmf is ignored at other byte positions. the itmfen and itmfh4 bits are located in the master incoming configuration register. itmf is sampled on the rising edge of sclk. ispe input 48 the active high incoming synchronous payload envelope (ispe) signal identifies the bytes within the transport envelope frame on the din[7:0] bus that carry the au3 or au4 virtual containers, and sts-1 synchronous payload envelopes. ispe must be brought high to mark each such byte. ispe is sampled on the rising edge of sclk.
pm5361 tupp data sheet pmc-920526 issue 8 tributary unit payload processor proprietary and confidential to pmc-sierra, inc., and for its customers internal use 13 pin name type pin no. function ipar input 70 the incoming stream parity (ipar) signal carries the parity of the incoming signals. the parity calculation encompasses the ic1j1 signal, the ispe signal and the din[7:0] bus. ic1j1 and ispe can be included in the parity calculation by setting the incic1j1 and incispe register bits respectively high. odd parity is selected by setting the iop register bit high, and even parity is selected by setting the iop bit low. the incic1j1, incispe and iop bits are located in the master incoming configuration register. ipar is sampled on the rising edge of sclk. oc1j1 input 127 the outgoing c1/j1 frame pulse (oc1j1) marks the transport envelope and synchronous payload envelope frame boundaries on the dout[7:0] bus. when the oj1en register bit is set low, oc1j1 pulses high to mark the first c1 byte of the transport envelope frame on the dout[7:0] bus. the position of the j1 bytes is implicit and fixed to the bytes immediately following the last c1 byte. when the oj1en register bit is set high, the oc1j1 signal pulses high while ispe is low to mark the first c1 byte of the transport envelope frame on the dout[7:0] bus and pulses high while ospe is high to mark each of the j1 bytes of the synchronous payload envelope(s) on the dout[7:0] bus. oc1j1 must be present at every occurrence of the first c1 byte and all j1 bytes. a v1 pulse added to the oc1j1 input will be ignored by the tupp. the oj1en bit is located in the master outgoing configuration register. oc1j1 is sampled on the rising edge of sclk.
pm5361 tupp data sheet pmc-920526 issue 8 tributary unit payload processor proprietary and confidential to pmc-sierra, inc., and for its customers internal use 14 pin name type pin no. function otmf input 125 the active high outgoing tributary multiframe (otmf) signal identifies the first frame of the tributary multiframe for each au3, or au4 administrative unit, and sts-1 synchronous payload envelope. otmf is selectable to pulse high during the v1 byte of the first tributary or during the h4 byte of the path overhead which indicates that the next frame is the first frame of the tributary multiframe. selection between marking v1 or h4 bytes is controlled by the otmfh4 bit located in the master outgoing configuration register. pulses on otmf are only effective during the h4 or v1 byte positions, as appropriate. otmf is ignored at other byte positions. otmf is sampled on the rising edge of sclk. ospe input 132 the active high outgoing synchronous payload envelope (ospe) signal identifies the bytes within the transport envelope frame on the dout[7:0] bus that carry the au3 or au4 virtual container(s), and the sts-1 synchronous payload envelopes. when the oj1en register bit is set high, ospe must be set high to mark each such byte. when the oj1en bit is set low, the outgoing virtual container (synchronous payload envelope) is locked with the j1 byte immediately following the c1 byte. ospe is ignored. dout[7:0], otspe, and otv5 contain valid data only for bytes in the au3 or au4 virtual container(s), or the sts-1 synchronous payload envelopes. their contents should be ignored for bytes in the transport overhead. the oj1en bit is located in the master outgoing configuration register. ospe is sampled on the rising edge of sclk.
pm5361 tupp data sheet pmc-920526 issue 8 tributary unit payload processor proprietary and confidential to pmc-sierra, inc., and for its customers internal use 15 pin name type pin no. function din[0] din[1] din[2] din[3] din[4] din[5] din[6] din[7] input 54 56 58 60 62 64 66 68 the data input bus (din[7:0]) carries sonet/sdh frame data in byte serial format. din[7] is the most significant bit, corresponding to bit 1 of each serial word, the bit transmitted first. din[0] is the least significant bit, corresponding to bit 8 of each serial word, the last bit transmitted. the din[7:0] bus is sampled on the rising edge of sclk. dout[0] dout[1] dout[2] dout[3] dout[4] dout[5] dout[6] dout[7] output 110 108 106 104 97 95 93 91 the data output bus (dout[7:0]) carries sonet/sdh frame data in byte serial format. dout[7] is the most significant bit, corresponding to bit 1 of each serial word, the bit transmitted first dout[0] is the least significant bit, corresponding to bit 8 of each serial word, the last bit transmitted. dout[7:0] contains valid data only for bytes in the au3 or au4 virtual container(s), or the sts-1 synchronous payload envelopes. its contents should be ignored for bytes in the transport overhead. the dout[7:0] bus is updated on the rising edge of sclk. opar output 89 the outgoing stream parity (opar) signal carries the parity of the outgoing data stream. odd parity is selected by setting the oop register bit in the master parity configuration register high, and even parity is selected by setting the oop bit low. opar is updated on the rising of sclk.
pm5361 tupp data sheet pmc-920526 issue 8 tributary unit payload processor proprietary and confidential to pmc-sierra, inc., and for its customers internal use 16 pin name type pin no. function otspe output 134 the outgoing tributary synchronous payload envelope (otspe) signal marks the bytes carrying the tributary synchronous payload envelope(s). otspe is set high to mark each such byte on the dout[7:0] bus. otspe, contains valid data only for bytes in the au3 or au4 virtual container(s), or the sts-1 synchronous payload envelopes. its contents should be ignored for bytes in the transport overhead. otspe is updated on the rising edge of sclk. otv5 output 136 the outgoing tributary v5 byte (otv5) signal marks the various tributary v5 bytes. otv5 is set high to mark each tributary v5 byte on the dout[7:0] bus. when the output tributary is a tu3, otv5 marks the j1 byte of the tu3. otv5 contains valid data only for bytes in the au3 or au4 virtual container(s), or the sts-1 synchronous payload envelopes. its contents should be ignored for bytes in the transport overhead. otv5 is updated on the rising edge of sclk. mbeb input 14 the active low motorola bus enable (mbeb) signal configures the tupp for motorola bus mode where the rdb/e signal functions as e, and the wrb/rwb signal functions as rwb. when mbeb is high, the tupp is configured for intel bus mode where the rdb/e signal functions as rdb. the mbeb input has an integral pull up resistor. csb input 13 the active low chip select (csb) signal is low during tupp register accesses.
pm5361 tupp data sheet pmc-920526 issue 8 tributary unit payload processor proprietary and confidential to pmc-sierra, inc., and for its customers internal use 17 pin name type pin no. function rdb/ input 35 the active low read enable (rdb) signal is low during tupp register read accesses while in intel bus mode. the tupp drives the d[7:0] bus with the contents of the addressed register while rdb and csb are low. e the active high external access (e) signal is high during tupp register access while in motorola bus mode. wrb/ input 37 the active low write strobe (wrb) signal is low during a tupp register write accesses while in intel bus mode. the d[7:0] bus contents are clocked into the addressed register on the rising wrb edge while csb is low. rwb the read/write select (rwb) signal selects between tupp register read and write accesses while in motorola bus mode. the tupp drives the d[7:0] bus with the contents of the addressed register while csb is low and rwb and e are high. the d[7:0] bus contents are clocked into the addressed register on the falling e edge while csb and rwb are low. d[0] d[1] d[2] d[3] d[4] d[5] d[6] d[7] i/o 15 16 17 18 23 24 25 26 the bidirectional data bus d[7:0] is used during tupp register read and write accesses.
pm5361 tupp data sheet pmc-920526 issue 8 tributary unit payload processor proprietary and confidential to pmc-sierra, inc., and for its customers internal use 18 pin name type pin no. function a[0] a[1] a[2] a[3] a[4] a[5] a[6] input 4 5 6 7 8 9 10 the address bus a[7:0] selects specific registers during tupp register accesses. a[7]/trs 11 the test register select (trs) signal selects between normal and test mode register accesses. trs is high during test mode register accesses, and is low during normal mode register accesses. trs has an integral pull down resistor. rstb input 31 the active low reset (rstb) signal provides an asynchronous tupp reset. rstb is a schmitt triggered input with an integral pull up resistor. ale input 33 the address latch enable (ale) is active high and latches the address bus a[7:0] when low. when ale is high, the internal address latches are transparent. it allows the tupp to interface to a multiplexed address/data bus. ale has an integral pull up resistor. intb od output 28 the active low interrupt (intb) signal goes low when a tupp interrupt source is active. intb returns high when the interrupt is acknowledged via an appropriate register access. intb is an open drain output.
pm5361 tupp data sheet pmc-920526 issue 8 tributary unit payload processor proprietary and confidential to pmc-sierra, inc., and for its customers internal use 19 pin name type pin no. function vddi1 vddi2 vddi3 vddi4 vddi5 vddi6 power 20 46 72 101 131 155 the core power (vddi1 - vddi6) pins should be connected to a well decoupled +5 v dc in common with vddo. vssi1 vssi2 vssi3 vssi4 vssi5 vssi6 ground 21 50 74 100 128 151 the core ground (vssi1 - vssi6) pins should be connected to gnd in common with vsso. vddo1 vddo2 vddo3 vddo4 vddo5 vddo6 power 19 87 102 113 130 154 the pad ring power (vddo1 - vddo6) pins should be connected to a well decoupled +5 v dc in common with vddi. vsso1 vsso2 vsso3 vsso4 vsso5 vsso6 vsso7 vsso8 ground 22 29 86 99 112 129 138 152 the pad ring ground (vsso1 - vsso8) pins should be connected to gnd in common with vssi.
pm5361 tupp data sheet pmc-920526 issue 8 tributary unit payload processor proprietary and confidential to pmc-sierra, inc., and for its customers internal use 20 pin name type pin no. function vsst1 vsst2 vsst3 vsst4 vsst5 vsst6 vsst7 vsst8 vsst9 vsst10 vsst11 vsst12 vsst13 vsst14 vsst15 vsst16 vsst17 vsst18 vsst19 vsst20 vsst21 vsst22 vsst23 vsst24 ground 1 2 3 38 39 40 41 42 43 78 79 80 81 82 83 118 119 120 121 122 123 158 159 160 the thermal ground (vsst1 - vsst24) pins should be connected to gnd in common with vssi and vsso. they may also be left floating. the vsst pins may be electrically connected together (fused) and connected to the back of the die to improve the thermal characteristics of the package.
pm5361 tupp data sheet pmc-920526 issue 8 tributary unit payload processor proprietary and confidential to pmc-sierra, inc., and for its customers internal use 21 notes on pin description: 1. all tupp inputs and bidirectionals present minimum capacitive loading and operate at ttl logic levels. 2. all tupp digital outputs and bidirectionals have 4 ma drive capability. 3. the vsso and vssi ground pins are not internally connected together. failure to connect these pins externally may cause malfunction or damage the tupp. 4. the vddo and vddi power pins are not internally connected together. failure to connect these pins externally may cause malfunction or damage the tupp.
pm5361 tupp data sheet pmc-920526 issue 8 tributary unit payload processor proprietary and confidential to pmc-sierra, inc., and for its customers internal use 22 9 functional description 9.1 input bus demultiplexer the input bus demultiplexer captures data sampled on the din bus and distributes this data to the three tributary payload processors within the tupp. the input bus demultiplexer also provides timing signals for the other blocks within the tupp. the system clock, sclk, is buffered and distributed to the tributary payload processors and the output bus multiplexer. frame alignment signals for the incoming data stream, ic1j1, itmf, and ispe, are sampled, buffered and distributed to the tributary payload processors (tpps). in order to have synchronous operation of the tpps with a single clock, the incoming data and control signals may be delayed by up to two system clock cycles before distribution to the tpp. the delay is used to align the incoming data with the outgoing data at each tpp. the amount of delay is adjusted such that the separation of the incoming sts/au frame and the outgoing frame at each tpp appears to be in multiples of three sclk periods. when configured for au4 mode, the input bus demultiplexer provides the necessary timing coordination between the three tributary payload processors. the single j1 byte marker input on ic1j1 is retimed and distributed to each of the three tributary payload processors. the tributary multiframe detected by tpp #1 is distributed to the two other tpps, as tpp #1 is the only one receiving a valid h4 byte. 9.2 output bus multiplexer the output bus multiplexer gathers data from the three tributary payload processors within the tupp and multiplexes this data onto the dout[7:0] bus. it also multiplexes signals from each tributary payload processor that mark tributary spes and tributary v5 bytes onto the shared otspe and otv5 signals. the output bus multiplexer also provides timing signals for other blocks within the tupp. frame alignment signals for the outgoing data stream, oc1j1, ospe and otmf, are sampled, buffered and distributed to the tributary payload processors (tpps). the output bus multiplexer contains a four frame counter that will flywheel in the absence of an active otmf input, internally generating tributary multiframe timing for the outgoing data stream. when configured for locked output mode, i.e. when oj1en is low, the output bus multiplexer will internally
pm5361 tupp data sheet pmc-920526 issue 8 tributary unit payload processor proprietary and confidential to pmc-sierra, inc., and for its customers internal use 23 generate j1 and spe timing for the outgoing data stream that corresponds to the j1 bytes following the c1 bytes and no pointer justifications at the sts-1 (au3) or au4 level. this timing drives the outputs of the three tributary payload processors, substituting for the function otherwise provided by the oc1j1 and ospe inputs. when configured for au4 mode, the output bus multiplexer provides the necessary timing coordination between the three tributary payload processors. this consists of deriving vc4 framing from the single j1 byte marker input on oc1j1 and distributing this to each tributary payload processor. 9.3 tributary payload processor each tributary payload processor processes the tributaries within an sts-1, au3, or tug3. each tpp can be configured to process any legal mix of vt1.5s, vt2s, vt3s, or vt6s that can be carried in an sts-1 or any legal mix of tu11s, tu12s, tu2s, or tu3s, that can be carried in an au3 or tug3. the number of tributaries managed by each tpp ranges from 1 (when configured to process a single tu3) to 28 (when configured to process all vt1.5s or all tu11s). 9.3.1 clock generator the clock generator derives various clocks from the 19.44 mhz system clock and distributes them to other blocks within the tributary payload processor. the overall design is totally synchronous, with processing occurring at a 6.48 mhz rate in each tributary payload processor. 9.3.2 incoming timing generator the incoming timing generator identifies the incoming tributary being processed at any given point in time. based on the configuration of the tpp (it can process various mixes of tributary types), the incoming timing generator extracts the sts- 1 spe, vc3, or a single tug3 from a vc4, and identifies the bytes within these envelopes that correspond to various types of overhead and those that carry specific tributaries to be processed. the h4 byte is identified for the incoming multiframe detector so that it can determine the incoming tributary multiframe boundaries. the identification of specific tributaries allows the pointer interpreter to be time-sliced across the mix of tributaries present in the incoming data stream. the identification of the v1-v3 bytes of vts, or tus (or h1-h3 bytes in the case of tu3s) allows the pointer interpreter to function.
pm5361 tupp data sheet pmc-920526 issue 8 tributary unit payload processor proprietary and confidential to pmc-sierra, inc., and for its customers internal use 24 9.3.3 incoming multiframe detector the incoming multiframe detector frames to the tributary multiframe encoded into the h4 bytes. it aligns a fly-wheeling multiframe counter to the alignment indicated by the h4 bytes when confidence is achieved in the h4 bytes. a change of incoming tributary multiframe occurs when the h4 bytes cycle error free and in correct sequence for four frames, and the detected alignment is new. the incoming multiframe detector is disabled and the multiframe is indicated by the itmf input signal, when itmf is enabled through the itmfen register bit. 9.3.4 pointer interpreter the pointer interpreter is a time-sliced state machine that can process up to 28 independent tributaries. the state vector is saved in ram as directed by the incoming timing generator. the pointer interpreter processes the incoming tributary pointers such that all bytes within the tributary synchronous payload envelope can be identified and written into the unique payload buffer for the tributary in question. a marker that tags the v5 byte (or j1 byte in the case of a tu3) is passed through the payload buffer. the incoming timing generator directs the pointer interpreter to the correct payload buffer for the tributary being processed. loss of pointer status is captured in microprocessor readable registers for each tributary and interrupts can optionally be generated upon loss of pointer and pointer acquisition. the pointer interpreter detects tributary path ais and suppresses the loss of pointer indication that would otherwise occur. the pointer interpreter passes this information to the pointer generator triggering path ais insertion into the corresponding outgoing tributary. the pointer generator can be configured to insert tributary path ais into outgoing tributaries if loss of pointer is detected on the associated incoming tributary. 9.3.5 payload buffer the payload buffer is a bank of fifo buffers. it is synchronous in operation and is based on a time-sliced ram. the three 19.44 mhz clock cycles in each 6.48 mhz period are shared between the read and write operations. the pointer interpreter writes tributary payload data and the v5 (or tu3 j1) tag into the payload buffer. a 16 byte fifo buffer is provided for each of the (up to 28) tributaries. address information is also passed through the payload buffer to allow fifo fill status to be determined by the pointer generator.
pm5361 tupp data sheet pmc-920526 issue 8 tributary unit payload processor proprietary and confidential to pmc-sierra, inc., and for its customers internal use 25 9.3.6 outgoing timing generator the outgoing timing generator identifies the outgoing tributary byte being processed. based on the configuration of the tpp , the outgoing timing generator effectively constructs the sts-1 spe, vc3, or vc4, and identifies the bytes within these envelopes that correspond to various types of overhead and bytes that carry specific tributaries. the identification of specific tributaries allows the pointer generator to be time-sliced across the mix of tributaries to be sourced in the outgoing data stream. the identification of the v1-v3 bytes of vts, or tus (h1-h3 bytes of tu3s) allows the pointer generator to function. the sequence h4 bytes is generated by each tributary payload processor and inserted into the outgoing administrative units. the six most significant bits of h4 are set to logic 1. the sequence of the remaining two h4 bits is determined by the otmf input when enabled or from the incoming multiframe alignment. 9.3.7 pointer generator the pointer generator is a time-sliced state machine that can process up to 28 independent tributaries. the state vector is saved in ram at the address associated with the current tributary. the pointer generator fills the outgoing tributary synchronous payload envelopes with bytes read from the associated fifo in the payload buffer for the current tributary. the pointer generator creates pointers in the v1-v3 bytes (or h1-h3 bytes in the case of tu3s) of the outgoing data stream. the marker that tags the v5 byte (or j1 byte in the case of a tu3) that is passed through the payload buffer is used to align the pointer. the outgoing timing generator directs the pointer generator to the fifo is the payload buffer associated with the tributary being processed. the pointer generator monitors the fill levels of the payload buffers and inserts outgoing pointer justifications as necessary to avoid fifo spillage. normally, the pointer generator has a fifo dead band of 4 bytes. the dead band can be collapse to one so that any incoming pointer justifications will be reflected by a corresponding outgoing justification with no attenuation. signals are output by the pointer generator that identify outgoing v5 bytes (or j1 bytes in the case of a tu3) and the tributary synchronous payload envelopes. these facilitate tributary performance monitoring external to the tupp. on a per tributary basis, tributary path ais and tributary idle (unequipped) can be inserted as controlled by microprocessor accessible registers. the idle code is selectable globally for the entire vc3 or tug3 to be all zeros or all ones. it is also possible to force an inverted new data flag on individual tributaries for the purpose of diagnosing downstream pointer processors. tributary path ais is automatically inserted into
pm5361 tupp data sheet pmc-920526 issue 8 tributary unit payload processor proprietary and confidential to pmc-sierra, inc., and for its customers internal use 26 outgoing tributaries if the pointer interpreter detects tributary path ais on the corresponding incoming tributary. 9.3.8 common bus interface the common bus interface allows microprocessor access to the registers within each tributary payload processor. it is used during normal operation and also during production test. it forms part of the overall microprocessor interface of the tupp. 9.4 microprocessor interface the microprocessor interface block provides normal and test mode registers, and the logic required to connect to the microprocessor interface. the normal mode registers are required for normal operation, and test mode registers are used to enhance the testability of the tupp. tributary based normal mode registers are arranged in order of transmission; tu #1 in tug2 #1 is the first tributary transmitted, while tu #4 in tug2 #7 is the last. the register set is accessed as follows: 9.5 register memory map address register 00h tupp master incoming configuration 01h tupp master outgoing configuration 02h input signal activity monitor 03h tupp master reset and identity 04h tributary payload processor #1 configuration 05h tributary payload processor #2 configuration 06h tributary payload processor #3 configuration 07h tributary payload processor and h4 oof interrupt enable 08h tributary payload processor interrupt status and h4 oof status 09h parity error and h4 oof interrupt 0ah-1fh reserved 20h tpp #1, tu3, or tu #1 in tug2 #1, configuration and status
pm5361 tupp data sheet pmc-920526 issue 8 tributary unit payload processor proprietary and confidential to pmc-sierra, inc., and for its customers internal use 27 address register 21h tpp #1, tu #1 in tug2 #2, configuration and status 22h tpp #1, tu #1 in tug2 #3, configuration and status 23h tpp #1, tu #1 in tug2 #4, configuration and status 24h tpp #1, tu #1 in tug2 #5, configuration and status 25h tpp #1, tu #1 in tug2 #6, configuration and status 26h tpp #1, tu #1 in tug2 #7, configuration and status 27h tpp #1, tu3 or tu #1 in tug2 #1 to tug2 #7, lop interrupt 28h tpp #1, tu #2 in tug2 #1, configuration and status 29h tpp #1, tu #2 in tug2 #2, configuration and status 2ah tpp #1, tu #2 in tug2 #3, configuration and status 2bh tpp #1, tu #2 in tug2 #4, configuration and status 2ch tpp #1, tu #2 in tug2 #5, configuration and status 2dh tpp #1, tu #2 in tug2 #6, configuration and status 2eh tpp #1, tu #2 in tug2 #7, configuration and status 2fh tpp #1, tu #2 in tug2 #1 to tug2 #7, lop interrupt 30h tpp #1, tu #3 in tug2 #1, configuration and status 31h tpp #1, tu #3 in tug2 #2, configuration and status 32h tpp #1, tu #3 in tug2 #3, configuration and status 33h tpp #1, tu #3 in tug2 #4, configuration and status 34h tpp #1, tu #3 in tug2 #5, configuration and status 35h tpp #1, tu #3 in tug2 #6, configuration and status 36h tpp #1, tu #3 in tug2 #7, configuration and status 37h tpp #1, tu #3 in tug2 #1 to tug2 #7, lop interrupt 38h tpp #1, tu #4 in tug2 #1, configuration and status 39h tpp #1, tu #4 in tug2 #2, configuration and status 3ah tpp #1, tu #4 in tug2 #3, configuration and status 3bh tpp #1, tu #4 in tug2 #4, configuration and status
pm5361 tupp data sheet pmc-920526 issue 8 tributary unit payload processor proprietary and confidential to pmc-sierra, inc., and for its customers internal use 28 address register 3ch tpp #1, tu #4 in tug2 #5, configuration and status 3dh tpp #1, tu #4 in tug2 #6, configuration and status 3eh tpp #1, tu #4 in tug2 #7, configuration and status 3fh tpp #1, tu #4 in tug2 #1 to tug2 #7, lop interrupt 40h-5fh tributary payload processor #2 registers 60h-7fh tributary payload processor #3 registers 80h master test 81h-ffh reserved for test for all register accesses, csb must be low.
pm5361 tupp data sheet pmc-920526 issue 8 tributary unit payload processor proprietary and confidential to pmc-sierra, inc., and for its customers internal use 29 10 normal mode register description normal mode registers are used to configure and monitor the operation of the tupp. normal mode registers (as opposed to test mode registers) are selected when a[7] is low. notes on normal mode register bits: 1. writing values into unused register bits has no effect. however, to ensure software compatibility with future, feature-enhanced versions of the product, unused register bits must be written with logic 0. reading back unused bits can produce either a logic 1 or a logic 0; hence unused register bits should be masked off by software when read. 2. all configuration bits that can be written into can also be read back. this allows the processor controlling the tupp to determine the programming state of the block. 3. writable normal mode register bits are cleared to logic 0 upon reset unless otherwise noted. 4. writing into read-only normal mode register bit locations does not affect tupp operation unless otherwise noted.
pm5361 tupp data sheet pmc-920526 issue 8 tributary unit payload processor proprietary and confidential to pmc-sierra, inc., and for its customers internal use 30 register 00h: master incoming configuration bit type function default bit 7 r/w ipe 0 bit 6 r/w autoais 0 bit 5 r/w incispe 0 bit 4 r/w incic1j1 0 bit 3 r/w iop 0 bit 2 r/w itmfh4 0 bit 1 r/w itmfen 0 bit 0 r/w iconcat 0 this register configures the tupp functionality that are related to the incoming data stream. iconcat: when set high, the iconcat bit configures the incoming section of the tupp to operate in au4 mode. when the iconcat bit is set low, the incoming section operates in au3 mode (or equivalently, sts-1 mode). itmfen: when set high, the itmfen bit enables the tupp to use the itmf input signal to locate tributary multiframe boundaries. the h4 bytes in the incoming data stream are ignored. when itmfen is set low, the h4 bytes are used to locate the boundaries, and the itmf signal is ignored. itmfh4: the itmfh4 bit selects the location of the itmf in the tributary multiframe. when itmfh4 is set high, itmf is pulsed high to mark the h4 byte which indicates that the next au3/4 or sts-1 frame is the first frame of the tributary multiframe. when itmfh4 is set low, itmf marks the v1 byte of the first tributary. itmfh4 is ignored if itmf is disabled by setting the itmfen bit low. iop: the iop bit controls the expected parity on the incoming parity signal ipar. when iop is set high, the parity of the parity signal set, together with ipar is
pm5361 tupp data sheet pmc-920526 issue 8 tributary unit payload processor proprietary and confidential to pmc-sierra, inc., and for its customers internal use 31 expected to be odd. when iop is set low, the expected parity is even. membership of the parity signal set always includes din[7:0], and may include input signals ic1j1 and ispe as controlled by the incic1j1 and incispe bits, respectively. incic1j1: the incic1j1 bit controls the whether the 1c1j1 input signal participates in the incoming parity calculations. when incic1j1 is set high, the parity signal set includes the ic1j1 input. when incic1j1 is set low, parity is calculated without regard to the state of ic1j1. selection of odd or even parity is controlled by the iop bit. incispe: the incispe bit controls the whether the ispe input signal participates in the incoming parity calculations. when incispe is set high, the parity signal set includes the ispe input. when incispe is set low, parity is calculated without regard to the state of ispe. selection of odd or even parity is controlled by the iop bit. autoais: the autoais bit is an active high ais insertion enable. when autoais is set high, ais is automatically generated on the outgoing data stream for all tributaries that exhibit a lop state. when autoais is set low, the generation of ais on the outgoing data stream is inhibited. the negation of ais occurs at tributary multiframe boundaries. ipe: the ipe bit is an active high interrupt enable. when ipe is set high, the occurrence of a parity error on the incoming parity signal set will cause an interrupt to be asserted on the interrupt (intb) output. when ipe is set low, incoming parity errors will not cause an interrupt.
pm5361 tupp data sheet pmc-920526 issue 8 tributary unit payload processor proprietary and confidential to pmc-sierra, inc., and for its customers internal use 32 register 01h: master outgoing configuration bit type function default bit 7 unused x bit 6 unused x bit 5 unused x bit 4 unused x bit 3 r/w oop 0 bit 2 r/w otmfh4 0 bit 1 r/w oj1en 0 bit 0 r/w oconcat 0 this register configures the tupp functionality that are related to the outgoing data stream. oconcat: when set high, the oconcat bit configures the outgoing section of the tupp to operate in au4 mode. when the oconcat bit is set low, the outgoing section operates in au3 mode (or equivalently, sts-1 mode). oj1en: when set high, the oj1en bit enables the tupp output bus to operate in floating mode where the oc1j1 signal marks the first c1 byte and the j1 bytes in the outgoing data stream, dout[7:0]. the ospe input is used to distinguish between bytes in the transport overhead and the payload envelope, and consequently c1 and j1. only one j1 byte, and one vc or concatenated spe, are expected to be marked when configured for au4 mode (oconcat set high). when the oj1en bit is low, the tupp output bus operates in locked mode where the oc1j1 signal marks the first c1 byte only in the outgoing data stream, dout[7:0]. in this mode, the ospe input must be logic zero for the c1 byte. the tupp defaults to fixed output timing where the j1 bytes of the sts-1, au3 or au4 synchronous payload envelopes are assumed to immediately follow the c1 bytes.
pm5361 tupp data sheet pmc-920526 issue 8 tributary unit payload processor proprietary and confidential to pmc-sierra, inc., and for its customers internal use 33 in either floating or locked mode, the otmf input is used to establish the transmit tributary multiframe boundaries on the outgoing data stream dout[7:0]. otmfh4: the otmfh4 bit selects the location of the otmf in the tributary multiframe. when otmfh4 is set high, otmf is pulsed high to mark the h4 byte which indicates that the next au3/4 or sts-1 frame is the first frame of the tributary multiframe. when otmfh4 is set low, otmf marks the v1 byte of the first tributary. oop: the oop bit controls the parity placed on the outgoing parity signal opar. when oop is set low, the parity of outgoing data stream dout[7:0], together with opar is even. when oop is set high, the parity is odd.
pm5361 tupp data sheet pmc-920526 issue 8 tributary unit payload processor proprietary and confidential to pmc-sierra, inc., and for its customers internal use 34 register 02h: input signal activity monitor bit type function default bit 7 r otmfa x bit 6 r ospea x bit 5 r oc1j1a x bit 4 r dina x bit 3 r itmfa x bit 2 r ispea x bit 1 r ic1j1a x bit 0 r sclka x this register provides activity monitoring on major tupp inputs. when a monitored input makes a low to high transition, the corresponding register bit is set high. the bit will remain high until this register is read, at which point, all the bits in this register are cleared. a lack of transitions is indicated by the corresponding register bit reading low. this register should be read at periodically to detect for stuck at conditions. sclka: the sclk active (sclka) bit monitors for low to high transitions on the sclk input. sclka is set high on a rising edge of sclk, and is set low when this register is read. ic1j1a: the ic1j1 active (ic1j1a) bit monitors for low to high transitions on the ic1j1 input. ic1j1a is set high on a rising edge of ic1j1, and is set low when this register is read. ispea: the ispe active (ispea) bit monitors for low to high transitions on the ispe input. ispea is set high on a rising edge of ispe, and is set low when this register is read.
pm5361 tupp data sheet pmc-920526 issue 8 tributary unit payload processor proprietary and confidential to pmc-sierra, inc., and for its customers internal use 35 itmfa: the itmf active (itmfa) bit monitors for low to high transitions on the itmf input. itmfa is set high on a rising edge of itmf, and is set low when this register is read. dina: the din bus active (dina) bit monitors for low to high transitions on the din[7:0] inputs. dina is set high when rising edges have been observed on all the signals on the din[7:0] bus, and is set low when this register is read. oc1j1a: the oc1j1 active (oc1j1a) bit monitors for low to high transitions on the oc1j1 input. oc1j1a is set high on a rising edge of oc1j1, and is set low when this register is read. ospea: the ospe active (ospea) bit monitors for low to high transitions on the ospe input. ospea is set high on a rising edge of ospe, and is set low when this register is read. otmfa: the otmf active (otmfa) bit monitors for low to high transitions on the otmf input. otmfa is set high on a rising edge of otmf, and is set low when this register is read.
pm5361 tupp data sheet pmc-920526 issue 8 tributary unit payload processor proprietary and confidential to pmc-sierra, inc., and for its customers internal use 36 register 03h: master reset and identity bit type function default bit 7 r/w reset 0 bit 6 r id[6] 0 bit 5 r id[5] 0 bit 4 r id[4] 0 bit 3 r id[3] 0 bit 2 r id[2] 0 bit 1 r id[1] 0 bit 0 r id[0] 1 this register allows the revision of the tupp to be read by software permitting graceful migration to support for newer, feature enhanced versions of the tupp, should revision of the tupp occur. it also provides software reset capability. id[6:0]: the id bits can be read to provide a binary tupp revision number. reset: the reset bit allows the tupp to be reset under software control. if the reset bit is a logic 1, the entire tupp is held in reset. this bit is not self- clearing. therefore, a logic 0 must be written to bring the tupp out of reset. holding the tupp in a reset state places it into a low power, stand-by mode. a hardware reset clears the reset bit, thus negating the software reset. otherwise the effect of a software reset is equivalent to that of a hardware reset.
pm5361 tupp data sheet pmc-920526 issue 8 tributary unit payload processor proprietary and confidential to pmc-sierra, inc., and for its customers internal use 37 register 04h: tributary payload processor #1 configuration bit type function default bit 7 r/w tppen 0 bit 6 unused x bit 5 unused x bit 4 r/w icode 0 bit 3 r/w nofilt 0 bit 2 r/w tu3 0 bit 1 r/w itug3 0 bit 0 r/w otug3 0 this register is used to configure the major operational modes of tributary payload processor #1. otug3: when set high, the otug3 bit configures the tributary payload processor to process tug2s that have been mapped into a tug3 in the outgoing data stream. when low, the tributary payload processor defaults to processing tug2s that have been mapped into a vc3, or equivalently, vt groups that have been mapped into an sts-1. itug3: when set high, the itug3 bit configures the tributary payload processor to process tug2s that have been mapped into a tug3 in the incoming data stream. when low, the tributary payload processor defaults to processing tug2s that have been mapped into a vc3, or equivalently, vt groups that have been mapped into an sts-1. tu3: when set high, the tu3 bit configures the tributary payload processor to process a single tu3 that has been mapped into a tug3. when the tu3 bit is set high, the itug3 and otug3 bits should be set low. both the incoming and outgoing streams are affected simultaneously by the tu3 bit. when in tu3 mode, registers 20h and 27h reflect tu3 status and configuration, all other registers relating to tug2s and the tributaries within tug2s are
pm5361 tupp data sheet pmc-920526 issue 8 tributary unit payload processor proprietary and confidential to pmc-sierra, inc., and for its customers internal use 38 disabled; data written is ignored, data read is invalid. when not in tu3 mode, register 20h reflects status and configuration of tug2 #1, tu #1 and register 27h reflect lop interrupt status of tu #1 in all seven tug #2s. nofilt: the nofilt bit controls the processing of incoming tributary pointers. when a logic 0 is written to this location, illegal variations from normal tributary pointer value (i.e. changes which do not correspond to pointer justification events, and are not accompanied by a new data flag) are ignored unless a consistent new value is received three times consecutively. when a logic 1 is written to this location, variations take effect immediately and are passed through the payload buffer unfiltered. icode: the icode bit controls the value inserted into tributary bytes when idle insertion is enabled. when a logic 0 is written to this location, the idle code is chosen to be all zeros. setting icode to 1 sets the idle code to all ones. regardless of the idle code selected, a valid pointer and a valid v5 byte that tags the tributary as unequipped is inserted. in tu3 mode, icode must be set to 0 for the c2 byte to indicate unequipped. tppen: when set high, the tppen bit enables the operation of tributary payload processor #1. when tppen is low, tpp #1 is held in a low power, reset state. the data destined for tpp #1 is re-transmitted unchanged on the outgoing data stream. the amount of delay from the incoming to the outgoing data stream is a function of the separation between the ic1j1 and oc1j1 inputs. see the bypass functional timing diagram for details.
pm5361 tupp data sheet pmc-920526 issue 8 tributary unit payload processor proprietary and confidential to pmc-sierra, inc., and for its customers internal use 39 register 05h: tributary payload processor #2 configuration bit type function default bit 7 r/w tppen 0 bit 6 unused x bit 5 unused x bit 4 r/w icode 0 bit 3 r/w nofilt 0 bit 2 r/w tu3 0 bit 1 r/w itug3 0 bit 0 r/w otug3 0 this register is used to configure the major operational modes of tributary payload processor #2. otug3: when set high, the otug3 bit configures the tributary payload processor to process tug2s that have been mapped into a tug3 in the outgoing data stream. when low, the tributary payload processor defaults to processing tug2s that have been mapped into a vc3, or equivalently, vt groups that have been mapped into an sts-1. itug3: when set high, the itug3 bit configures the tributary payload processor to process tug2s that have been mapped into a tug3 in the incoming data stream. when low, the tributary payload processor defaults to processing tug2s that have been mapped into a vc3, or equivalently, vt groups that have been mapped into an sts-1. tu3: when set high, the tu3 bit configures the tributary payload processor to process a single tu3 that has been mapped into a tug3. when the tu3 bit is set high, the itug3 and otug3 bits should be set low. both the incoming and outgoing streams are affected simultaneously by the tu3 bit. when in tu3 mode, registers 40h and 47h reflect tu3 status and configuration, all other registers relating to tug2s and the tributaries within tug2s are
pm5361 tupp data sheet pmc-920526 issue 8 tributary unit payload processor proprietary and confidential to pmc-sierra, inc., and for its customers internal use 40 disabled; data written is ignored, and read data is invalid. when not in tu3 mode, register 40h reflects status and configuration of tug2 #1, tu #1 and register 47h reflect lop interrupt status of tu #1 in all seven tug #2s. nofilt: the nofilt bit controls the processing of incoming tributary pointers. when a logic 0 is written to this location, illegal variations from normal tributary pointer value (i.e. changes which do not correspond to pointer justification events, and are not accompanied by a new data flag) are ignored unless a consistent new value is received three times consecutively. when a logic 1 is written to this location, variations take effect immediately and are passed through the payload buffer unfiltered. icode: the icode bit controls the value inserted into tributary bytes when idle insertion is enabled. when a logic 0 is written to this location, the idle code is chosen to be all zeros. setting icode to 1 sets the idle code to all ones. regardless of the idle code selected, a valid pointer and a valid v5 byte that tags the tributary as unequipped is inserted. in tu3 mode, icode must be set to 0 for the c2 byte to indicate unequipped. tppen: when set high, the tppen bit enables the operation of tributary payload processor #2. when tppen is low, tpp #2 is held in a low power, reset state. the data destined for tpp #2 is re-transmitted unchanged on the outgoing data stream. the amount of delay from the incoming to the outgoing data stream is a function of the separation between the ic1j1 and oc1j1 inputs. see the bypass functional timing diagram for details.
pm5361 tupp data sheet pmc-920526 issue 8 tributary unit payload processor proprietary and confidential to pmc-sierra, inc., and for its customers internal use 41 register 06h: tributary payload processor #3 configuration bit type function default bit 7 r/w tppen 0 bit 6 unused x bit 5 unused x bit 4 r/w icode 0 bit 3 r/w nofilt 0 bit 2 r/w tu3 0 bit 1 r/w itug3 0 bit 0 r/w otug3 0 this register is used to configure the major operational modes of tributary payload processor #3. otug3: when set high, the otug3 bit configures the tributary payload processor to process tug2s that have been mapped into a tug3 in the outgoing data stream. when low, the tributary payload processor defaults to processing tug2s that have been mapped into a vc3, or equivalently, vt groups that have been mapped into an sts-1. itug3: when set high, the itug3 bit configures the tributary payload processor to process tug2s that have been mapped into a tug3 in the incoming data stream. when low, the tributary payload processor defaults to processing tug2s that have been mapped into a vc3, or equivalently, vt groups that have been mapped into an sts-1. tu3: when set high, the tu3 bit configures the tributary payload processor to process a single tu3 that has been mapped into a tug3. when the tu3 bit is set high, the itug3 and otug3 bits should be set low. both the incoming and outgoing streams are affected simultaneously by the tu3 bit. when in tu3 mode, registers 60h and 67h reflect tu3 status and configuration, all other registers relating to tug2s and the tributaries within tug2s are
pm5361 tupp data sheet pmc-920526 issue 8 tributary unit payload processor proprietary and confidential to pmc-sierra, inc., and for its customers internal use 42 disabled; data written is ignored and read data is invalid. when not in tu3 mode, register 60h reflects status and configuration of tug2 #1, tu #1 and register 67h reflect lop interrupt status of tu #1 in all seven tug #2s. nofilt: the nofilt bit controls the processing of incoming tributary pointers. when a logic 0 is written to this location, illegal variations from normal tributary pointer value (i.e. changes which do not correspond to pointer justification events, and are not accompanied by a new data flag) are ignored unless a consistent new value is received three times consecutively. when a logic 1 is written to this location, variations take effect immediately and are passed through the payload buffer unfiltered. icode: the icode bit controls the value inserted into tributary bytes when idle insertion is enabled. when a logic 0 is written to this location, the idle code is chosen to be all zeros. setting icode to 1 sets the idle code to all ones. regardless of the idle code selected, a valid pointer and a valid v5 byte that tags the tributary as unequipped is inserted. in tu3 mode, icode must be set to 0 for the c2 byte to indicate unequipped. tppen: when set high, the tppen bit enables the operation of tributary payload processor #3. when tppen is low, tpp #3 is held in a low power, reset state. the data destined for tpp #3 is re-transmitted unchanged on the outgoing data stream. the amount of delay from the incoming to the outgoing data stream is a function of the separation between the ic1j1 and oc1j1 inputs. see the bypass functional timing diagram for details.
pm5361 tupp data sheet pmc-920526 issue 8 tributary unit payload processor proprietary and confidential to pmc-sierra, inc., and for its customers internal use 43 register 07h: tpp and h4 oof interrupt enable bit type function default bit 7 unused x bit 6 unused x bit 5 r/w oof3e 0 bit 4 r/w oof2e 0 bit 3 r/w oof1e 0 bit 2 r/w tpp3e 0 bit 1 r/w tpp2e 0 bit 0 r/w tpp1e 0 this register provides interrupt enable of the three h4 byte framers and of the three tributary payload processors in the tupp. tpp1e: tpp1e is the interrupt enable bit for tributary payload processor #1 in the tupp. interrupts enabled at tributary processor #1 but masked by tpp1e will still be reported by the tpp1i bit, although the interrupt output will not be activated. interrupts disabled at tributary payload processor #1 will not be reported by the tpp1i bit. tpp2e: tpp2e is the interrupt enable bit for tributary processor #2 in the tupp. interrupts enabled at tributary payload processor #2 but masked by tpp2e will still be reported by the tpp2i bit, although the interrupt output will not be activated. interrupts disabled at tributary payload processor #2 will not be reported by the tpp2i bit. tpp3e: tpp3e is the interrupt enable bit for tributary payload processor #3 in the tupp. interrupts enabled at tributary processor #3 but masked by tpp3e will still be reported by the tpp3i bit, although the interrupt output will not be activated. interrupts disabled at tributary payload processor #3 will not be reported by the tpp3i bit.
pm5361 tupp data sheet pmc-920526 issue 8 tributary unit payload processor proprietary and confidential to pmc-sierra, inc., and for its customers internal use 44 oof1e: the oof1e bit is an interrupt enable bit for the h4 framer out of frame interrupt in tributary payload processor #1. when oof1e is set high, a change in the framer out of frame status will cause an interrupt to be generated on the intb output. interrupts are masked when oofe is set low. oof2e: the oof2e bit is an interrupt enable bit for the h4 framer out of frame interrupt in tributary payload processor #2. when oof2e is set high, a change in the framer out of frame status will cause an interrupt to be generated on the intb output. interrupts are masked when oofe is set low. when iconcat is set to logic 1 this interrupt enable bit should be set to logic 0. in the au4 mode the multiframe alignment is determined by the h4 byte framer in tributary payload processor #1. oof3e: the oof3e bit is an interrupt enable bit for the h4 framer out of frame interrupt in tributary payload processor #3. when oof3e is set high, a change in the framer out of frame status will cause an interrupt to be generated on the intb output. interrupts are masked when oofe is set low. when iconcat is set to logic 1 this interrupt enable bit should be set to logic 0. in the au4 mode the multiframe alignment is determined by the h4 byte framer in tributary payload processor #1.
pm5361 tupp data sheet pmc-920526 issue 8 tributary unit payload processor proprietary and confidential to pmc-sierra, inc., and for its customers internal use 45 register 08h: tpp interrupt status and h4 oof status bit type function default bit 7 unused x bit 6 unused x bit 5 r oof3v 0 bit 4 r oof2v 0 bit 3 r oof1v 0 bit 2 r tpp3i 0 bit 1 r tpp2i 0 bit 0 r tpp1i 0 this register provides interrupt status of the three h4 byte framers and of the three tributary payload processors in the tupp. tpp1i: tpp1i identifies tributary payload processor #1 as the source of a pending interrupt. it is necessary to read the lop interrupt status registers in tributary processor #1 to determine the event causing the interrupt and to clear the interrupt. interrupts disabled at tributary payload processor #1 will not be reported by the tpp1i bit. tpp2i: tpp2i identifies tributary payload processor #2 as the source of a pending interrupt. it is necessary to read the lop interrupt status registers in tributary processor #2 to determine the event causing the interrupt and to clear the interrupt. interrupts disabled at tributary payload processor #2 will not be reported by the tpp2i bit. tpp3i: tpp1i identifies tributary payload processor #3 as the source of a pending interrupt. it is necessary to read the lop interrupt status registers in tributary processor #3 to determine the event causing the interrupt and to clear the interrupt. interrupts disabled at tributary payload processor #3 will not be reported by the tpp3i bit.
pm5361 tupp data sheet pmc-920526 issue 8 tributary unit payload processor proprietary and confidential to pmc-sierra, inc., and for its customers internal use 46 oof1v: the oof1v bit indicates the status of the h4 byte framer in tributary payload processor #1. oof1v is set high when the h4 framer goes out of frame and is set low when it re-acquires frame. oof2v: the oof2v bit indicates the status of the h4 byte framer in tributary payload processor #2. oof2v is set high when the h4 framer goes out of frame and is set low when it re-acquires frame. when iconcat is set to logic 1 this status bit should be ignored since the multiframe alignment is determined by the h4 byte framer in tributary payload processor #1. oof3v: the oof3v bit indicates the status of the h4 byte framer in tributary payload processor #3. oof3v is set high when the h4 framer goes out of frame and is set low when it re-acquires frame. when iconcat is set to logic 1 this status bit should be ignored since the multiframe alignment is determined by the h4 byte framer in tributary payload processor #1.
pm5361 tupp data sheet pmc-920526 issue 8 tributary unit payload processor proprietary and confidential to pmc-sierra, inc., and for its customers internal use 47 register 09h: parity error and h4 oof interrupt bit type function default bit 7 r ipi 0 bit 6 unused x bit 5 r oof3i 0 bit 4 r oof2i 0 bit 3 rf oof1i 0 bit 2 unused x bit 1 unused x bit 0 unused x this register provides interrupt status of the h4 byte framers in the three tributary payload processor and of the input parity checker in the tupp. oof1i: the oof1i bit indicates a change of status in the h4 byte framer. interrupts are generated when the h4 framer in tributary payload processor #1 goes out of frame and when it re-acquires frame. the oof1i bit is set high when an out of frame event occurs and is cleared immediately following a read of this register, which also acknowledges and clears the interrupt. the oofi bit remains valid when interrupts are not enabled (oof1e set low) and may be polled to detect out of frame events. oof2i: the oof2i bit indicates a change of status in the h4 byte framer. interrupts are generated when the h4 framer in tributary payload processor #2 goes out of frame and when it re-acquires frame. the oof2i bit is set high when an out of frame event occurs and is cleared immediately following a read of this register, which also acknowledges and clears the interrupt. the oof2i bit remains valid when interrupts are not enabled (oof2e set low) and may be polled to detect out of frame events. oof3i: the oof3i bit indicates a change of status in the h4 byte framer. interrupts are generated when the h4 framer in tributary payload processor #2 goes out
pm5361 tupp data sheet pmc-920526 issue 8 tributary unit payload processor proprietary and confidential to pmc-sierra, inc., and for its customers internal use 48 of frame and when it re-acquires frame. the oof3i bit is set high when an out of frame event occurs and is cleared immediately following a read of this register, which also acknowledges and clears the interrupt. the oof3i bit remains valid when interrupts are not enabled (oof3e set low) and may be polled to detect out of frame events. ipi: the incoming parity error interrupt bit (ipi) is set high when a parity error is detected on the incoming parity signal set. if the ipe bit in the master incoming configuration register is set high, the interrupt output (intb) is activated. when this register is read, ipi (and the corresponding interrupt) is cleared.
pm5361 tupp data sheet pmc-920526 issue 8 tributary unit payload processor proprietary and confidential to pmc-sierra, inc., and for its customers internal use 49 register 20h, 40h, 60h: tu3, or tu #1 in tug2 #1, configuration and status bit type function default bit 7 r/w config[1] 1 bit 6 r/w config[0] 1 bit 5 r/w pf 0 bit 4 r lopv 0 bit 3 r/w lope 0 bit 2 r/w dlop 0 bit 1 r/w iidle 0 bit 0 r/w ipais 0 in tu3 mode (tu3 bit in tpp configuration register set high), this register reports the status and configures operational modes of the tu3 mapped into a tug3 handled by the tpp. out of tu3 mode, this register reports the status and configures the operational modes of tu #1 in tug2 #1. ipais: the ipais bit enables the insertion of path ais for tributary tu #1 in tug2 #1 or tu3 depending on whether the tpp is in tu3 mode. tributary path ais is inserted by forcing all ones into all tributary bytes. the ipais bit has precedence over the iidle and the dlop bits. iidle: the iidle bit enables the insertion of path idle for tributary tu #1 in tug2 #1 or tu3 depending on whether the tpp is in tu3 mode. tributary idle is inserted with the idle code in the tributary bytes, except for a valid pointer and a valid v5 byte that tags the tributary as unequipped. the idle code is selectable to be all zeros or all ones as controlled by the icode bit. in order for the c2 byte to be labelled unequipped, the icode bit must be set low in tu3 mode. the iidle bit has no effect when the ipais bit is set high. dlop: the dlop bit allows downstream pointer processing elements to be diagnosed. when dlop is set high, the new data flag (ndf) field of the outgoing payload pointer in tributary tu #1 in tug2 #1 or tu3 depending on
pm5361 tupp data sheet pmc-920526 issue 8 tributary unit payload processor proprietary and confidential to pmc-sierra, inc., and for its customers internal use 50 whether the tpp is in tu3 mode, is inverted to cause downstream pointer processing elements to enter a loss of pointer state. insertion of an inverted new data flag can occur in concert with the insertion of a normal idle (unequipped) indication as directed by the iidle bit. the dlop bit has no effect when the ipais bit is set high. lope: the lope bit enables loss of pointer interrupts for tributary tu #1 in tug2 #1 or tu3 depending on whether the tpp is in tu3 mode. when lope is set high, an interrupt is generated upon loss of pointer and upon re-acquisition. interrupts due to lop status change are masked when lope is set low. lopv: the lopv bit indicates the loss of pointer status of tributary tu #1 in tug2 #1 or tu3 depending on whether the tpp is in tu3 mode. pf: the pf bit enables pointer follower mode for tributary tu #1 in tug2 #1 or tu3 depending on whether the tpp is in tu3 mode. in pointer follower mode, the tributary fifo dead-zone is collapsed so that any variation is fifo depth will result in an outgoing pointer justification event. any tu pointer justification event on the corresponding incoming tributary, or an au pointer justification event affecting this tributary will cause an outgoing pointer justification event. config[1:0]: the config[1:0] bits specify the tributary configuration of tributary group tug2 #1. the config[1:0] bits have no effect in tu3 mode. the configuration specified by the config[1:0] bits are selected as follows: config[1] config[0] configuration active tu (vt) 0 0 tu2 (vt6) #1 0 1 vt3 #1, #2 1 0 tu12 (vt2) #1, #2, #3 1 1 tu11 (vt1.5) #1, #2, #3, #4
pm5361 tupp data sheet pmc-920526 issue 8 tributary unit payload processor proprietary and confidential to pmc-sierra, inc., and for its customers internal use 51 register 21h-26h, 41h-46h, 61h-66h: tu #1 in tug2 #2 to tug2 #7, configuration and status bit type function default bit 7 r/w config[1] 1 bit 6 r/w config[0] 1 bit 5 r/w pf 0 bit 4 r lopv 0 bit 3 r/w lope 0 bit 2 r/w dlop 0 bit 1 r/w iidle 0 bit 0 r/w ipais 0 this set of registers reports the status and configures the operational modes of tu #1 in tug2 #2 to tug2 #7. these registers have no effect in tu3 mode. ipais: the ipais bit enables the insertion of path ais for tributary tu #1 in the corresponding tug2. tributary path ais is inserted by forcing all ones into all tributary bytes. the ipais bit has precedence over the iidle and the dlop bits. iidle: the iidle bit enables the insertion of path idle for tributary tu #1 in the corresponding tug2. tributary idle is inserted with the idle code in the tributary bytes, except for a valid pointer and a valid v5 byte that tags the tributary as unequipped. the idle code is selectable to be all zeros or all ones as controlled by the icode bit. the iidle bit has no effect when the ipais bit is set high. dlop: the dlop bit allows downstream pointer processing elements to be diagnosed. when dlop is set high, the new data flag (ndf) field of the outgoing payload pointer in tributary tu #1 in the corresponding tug2 is inverted to cause downstream pointer processing elements to enter a loss of pointer state. insertion of an inverted new data flag can occur in concert with
pm5361 tupp data sheet pmc-920526 issue 8 tributary unit payload processor proprietary and confidential to pmc-sierra, inc., and for its customers internal use 52 the insertion of a normal idle (unequipped) indication as directed by the iidle bit. the dlop bit has no effect when the ipais bit is set high. lope: the lope bit enables loss of pointer interrupts for tributary tu #1 in the corresponding tug2. when lope is set high, an interrupt is generated upon loss of pointer and upon re-acquisition. interrupts due to lop status changes are masked when lope is set low. lopv: the lopv bit indicates the loss of pointer status of tributary tu #1 in the corresponding tug2. pf: the pf bit enables pointer follower mode for tributary tu #1 in the corresponding tug2. in pointer follower mode, the tributary fifo dead-zone is collapsed so that any variation is fifo depth will result in an outgoing pointer justification event. any tu pointer justification event on the corresponding incoming tributary, or an au pointer justification event affecting this tributary will cause an outgoing pointer justification event. config[1:0]: the config[1:0] bits specify the tributary configuration of the tug2 tributary group. the config[1:0] bits have no effect in tu3 mode. the configuration specified by the config[1:0] bits are selected as follows: config[1] config[0] configuration active tu (vt) 0 0 tu2 (vt6) #1 0 1 vt3 #1, #2 1 0 tu12 (vt2) #1, #2, #3 1 1 tu11 (vt1.5) #1, #2, #3, #4
pm5361 tupp data sheet pmc-920526 issue 8 tributary unit payload processor proprietary and confidential to pmc-sierra, inc., and for its customers internal use 53 register 27h, 47h, 67h: tu3 or tu #1 in tug2 #1 to tug2 #7, lop interrupt bit type function default bit 7 r/w accel 0 bit 6 r lop7i 0 bit 5 r lop6i 0 bit 4 r lop5i 0 bit 3 r lop4i 0 bit 2 r lop3i 0 bit 1 r lop2i 0 bit 0 r lop1i 0 this register is used to identify and acknowledge loss of pointer interrupts for the tributaries tu #1 in tug2 #1 to tug2 #7. it is also used to identify and acknowledge tu3 loss of pointer interrupts. lop1i: the lop1i bit identifies the source of loss of pointer interrupts. in tu3 mode, the lop1i bit reports and acknowledges lop interrupt of the tu3 pointer. out of tu3 mode, the lop1i bit reports and acknowledges lop interrupt of tu #1 in tug2 #1. interrupts are generated upon loss of pointer and upon re-acquisition. lop1i is set high when the corresponding loss of pointer event occurs and are cleared immediately following a read of this register, which also acknowledges and clears the interrupt. lop1i remains valid when interrupts are not enabled (lope set low) and may be polled to detect loss of pointer events. lop2i-lop7i: the lop2i to lop7i bits identify the source of loss of pointer interrupts. in tu3 mode, these bits are unused and will return a logic 0 when read. out of tu3 mode, the lop2i to lop7i bits report and acknowledge lop interrupt of tu #1 in tug2 #2 to tug2 #7, respectively. interrupts are generated upon loss of pointer and upon re-acquisition. an lop x i bit is set high when a loss of pointer event on the associated tributary (tu #1 in tug2 # x ) occurs and are cleared immediately following a read of this register, which also acknowledges and clears the interrupt. lop x i remains valid when interrupts
pm5361 tupp data sheet pmc-920526 issue 8 tributary unit payload processor proprietary and confidential to pmc-sierra, inc., and for its customers internal use 54 are not enabled (lope set low) and may be polled to detect loss of pointer events. accel: the accel bit is used for simulation purposes and must be written with a logic 0 for proper operation.
pm5361 tupp data sheet pmc-920526 issue 8 tributary unit payload processor proprietary and confidential to pmc-sierra, inc., and for its customers internal use 55 register 28h-2eh, 48h-4eh, 68h-6eh: tu #2 in tug2 #1 to tug2 #7, configuration and status bit type function default bit 7 r config[1] 1 bit 6 r config[0] 1 bit 5 r/w pf 0 bit 4 r lopv 0 bit 3 r/w lope 0 bit 2 r/w dlop 0 bit 1 r/w iidle 0 bit 0 r/w ipais 0 this set of registers reports the status and configures the operational modes of tu #2 in tug2 #1 to tug2 #7. these registers have no effect in tu3 mode. when the corresponding tug2 tributary group is configured to tu2 (vt6) mode, the associated register in this set has no effect. ipais: the ipais bit enables the insertion of path ais for tributary tu #2 in the corresponding tug2. tributary path ais is inserted by forcing all ones into all tributary bytes. the ipais bit has precedence over the iidle and the dlop bits. iidle: the iidle bit enables the insertion of path idle for tributary tu #2 in the corresponding tug2. tributary idle is inserted with the idle code in the tributary bytes, except for a valid pointer and a valid v5 byte that tags the tributary as unequipped. the idle code is selectable to be all zeros or all ones as controlled by the icode bit. the iidle bit has no effect when the ipais bit is set high. dlop: the dlop bit allows downstream pointer processing elements to be diagnosed. when dlop is set high, the new data flag (ndf) field of the outgoing payload pointer in tributary tu #2 in the corresponding tug2 is
pm5361 tupp data sheet pmc-920526 issue 8 tributary unit payload processor proprietary and confidential to pmc-sierra, inc., and for its customers internal use 56 inverted, causing downstream pointer processing elements to enter a loss of pointer state. insertion of an inverted new data flag can occur in concert with the insertion of a normal idle (unequipped) indication as directed by the iidle bit. the dlop bit has no effect when the ipais bit is set high. lope: the lope bit enables loss of pointer interrupts for tributary tu #2 in the corresponding tug2. when lope is set high, an interrupt is generated upon loss of pointer and upon re-acquisition. interrupts due to lop status change are masked when lope is set low. lopv: the lopv bit indicates the loss of pointer status of tributary tu #2 in the corresponding tug2. pf: the pf bit enables pointer follower mode for tributary tu #2 in the corresponding tug2. in pointer follower mode, the tributary fifo dead-zone is collapsed so that any variation is fifo depth will result in an outgoing pointer justification event. any tu pointer justification event on the corresponding incoming tributary, or an au pointer justification event affecting this tributary will cause an outgoing pointer justification event. config[1:0]: the config[1:0] bits are read-only and reflect the values written into the corresponding register of tu #1. the configuration specified by the config[1:0] bits are selected as follows: config[1] config[0] configuration active tu (vt) 0 0 tu2 (vt6) #1 0 1 vt3 #1, #2 1 0 tu12 (vt2) #1, #2, #3 1 1 tu11 (vt1.5) #1, #2, #3, #4
pm5361 tupp data sheet pmc-920526 issue 8 tributary unit payload processor proprietary and confidential to pmc-sierra, inc., and for its customers internal use 57 register 2fh, 4fh, 6fh: tu #2 in tug2 #1 to tug2 #7 bit type function default bit 7 unused x bit 6 r lop7i 0 bit 5 r lop6i 0 bit 4 r lop5i 0 bit 3 r lop4i 0 bit 2 r lop3i 0 bit 1 r lop2i 0 bit 0 r lop1i 0 this register is used to identify and acknowledge loss of pointer interrupts for the tributaries tu #2 in tug2 #1 to tug2 #7. lop1i-lop7i: the lop1i to lop7i bits identify the source of loss of pointer interrupts. in tu3 mode, these bits are unused and will return a logic 0 when read. when the corresponding tug2 tributary group is configured for tu2 (vt6) mode, the associated lop x i bit is unused and will return a logic 0 when read. when operational, the lop1i to lop7i bits report and acknowledge lop interrupts of tu #2 in tug2 #1 to tug2 #7, respectively. interrupts are generated upon loss of pointer and upon re-acquisition. an lop x i bit is set high when a loss of pointer event on the associated tributary occurs and are cleared immediately following a read of this register, which also acknowledges and clears the interrupt. lop x i remains valid when interrupts are not enabled (lope set low) and may be polled to detect loss of pointer events.
pm5361 tupp data sheet pmc-920526 issue 8 tributary unit payload processor proprietary and confidential to pmc-sierra, inc., and for its customers internal use 58 register 30h-36h, 50h-56h, 70h-76h: tu #3 in tug2 #1 to tug2 #7, configuration and status bit type function default bit 7 r config[1] 1 bit 6 r config[0] 1 bit 5 r/w pf 0 bit 4 r lopv 0 bit 3 r/w lope 0 bit 2 r/w dlop 0 bit 1 r/w iidle 0 bit 0 r/w ipais 0 this set of registers reports the status and configures the operational modes of tu #3 in tug2 #1 to tug2 #7. these registers have no effect in tu3 mode. when the corresponding tug2 tributary group is configured to tu2 (vt6) or vt3 mode, the associated register in this set has no effect. ipais: the ipais bit enables the insertion of path ais for tributary tu #3 in the corresponding tug2. tributary path ais is inserted by forcing all ones into all tributary bytes. the ipais bit has precedence over the iidle and the dlop bits. iidle: the iidle bit enables the insertion of path idle for tributary tu #3 in the corresponding tug2. tributary idle is inserted with the idle code in the tributary bytes, except for a valid pointer and a valid v5 byte that tags the tributary as unequipped. the idle code is selectable to be all zeros or all ones as controlled by the icode bit. the iidle bit has no effect when the ipais bit is set high. dlop: the dlop bit allows downstream pointer processing elements to be diagnosed. when dlop is set high, the new data flag (ndf) field of the outgoing payload pointer in tributary tu #3 in the corresponding tug2 is
pm5361 tupp data sheet pmc-920526 issue 8 tributary unit payload processor proprietary and confidential to pmc-sierra, inc., and for its customers internal use 59 inverted, causing downstream pointer processing elements to enter a loss of pointer state. insertion of an inverted new data flag can occur in concert with the insertion of a normal idle (unequipped) indication as directed by the iidle bit. the dlop bit has no effect when the ipais bit is set high. lope: the lope bit enables loss of pointer interrupts for tributary tu #3 in the corresponding tug2. when lope is set high, an interrupt is generated upon loss of pointer and upon re-acquisition. interrupts due to lop status change are masked when lope is set low. lopv: the lopv bit indicates the loss of pointer status of tributary tu #3 in the corresponding tug2. pf: the pf bit enables pointer follower mode for tributary tu #3 in the corresponding tug2. in pointer follower mode, the tributary fifo dead-zone is collapsed so that any variation is fifo depth will result in an outgoing pointer justification event. any tu pointer justification event on the corresponding incoming tributary, or an au pointer justification event affecting this tributary will cause an outgoing pointer justification event. config[1:0]: the config[1:0] bits are read-only and reflect the values written into the corresponding register of tu #1. the configuration specified by the config[1:0] bits are selected as follows: config[1] config[0] configuration active tu (vt) 0 0 tu2 (vt6) #1 0 1 vt3 #1, #2 1 0 tu12 (vt2) #1, #2, #3 1 1 tu11 (vt1.5) #1, #2, #3, #4
pm5361 tupp data sheet pmc-920526 issue 8 tributary unit payload processor proprietary and confidential to pmc-sierra, inc., and for its customers internal use 60 register 37h, 57h, 77h: tu #3 in tug2 #1 to tug2 #7, lop interrupt bit type function default bit 7 unused x bit 6 r lop7i 0 bit 5 r lop6i 0 bit 4 r lop5i 0 bit 3 r lop4i 0 bit 2 r lop3i 0 bit 1 r lop2i 0 bit 0 r lop1i 0 this register is used to identify and acknowledge loss of pointer interrupts for the tributaries tu #2 in tug2 #1 to tug2 #7. lop1i-lop7i: the lop1i to lop7i bits identify the source of loss of pointer interrupts. in tu3 mode, these bits are unused and will return a logic 0 when read. when the corresponding tug2 tributary group is configured for tu2 (vt6) or vt3 mode, the associated lop x i bit is unused and will return a logic 0 when read. when operational, the lop1i to lop7i bits report and acknowledge lop interrupts of tu #3 in tug2 #1 to tug2 #7, respectively. interrupts are generated upon loss of pointer and upon re-acquisition. an lop x i bit is set high when a loss of pointer event on the associated tributary occurs and are cleared immediately following a read of this register, which also acknowledges and clears the interrupt. lop x i remains valid when interrupts are not enabled (lope set low) and may be polled to detect loss of pointer events.
pm5361 tupp data sheet pmc-920526 issue 8 tributary unit payload processor proprietary and confidential to pmc-sierra, inc., and for its customers internal use 61 register 38h-3eh, 58h-5eh, 78h-7eh: tu #4 in tug2 #2 to tug2 #7, configuration and status bit type function default bit 7 r config[1] 1 bit 6 r config[0] 1 bit 5 r/w pf 0 bit 4 r lopv 0 bit 3 r/w lope 0 bit 2 r/w dlop 0 bit 1 r/w iidle 0 bit 0 r/w ipais 0 this set of registers reports the status and configures the operational modes of tu #4 in tug2 #1 to tug2 #7. these registers have no effect in tu3 mode. when the corresponding tug2 tributary group is configured to tu2 (vt6), vt3 or, tu12 (vt2) mode, the associated register in this set has no effect. ipais: the ipais bit enables the insertion of path ais for tributary tu #4 in the corresponding tug2. tributary path ais is inserted by forcing all ones into all tributary bytes. the ipais bit has precedence over the iidle and the dlop bits. iidle: the iidle bit enables the insertion of path idle for tributary tu #4 in the corresponding tug2. tributary idle is inserted with the idle code in the tributary bytes, except for a valid pointer and a valid v5 byte that tags the tributary as unequipped. the idle code is selectable to be all zeros or all ones as controlled by the icode bit. the iidle bit has no effect when the ipais bit is set high. dlop: the dlop bit allows downstream pointer processing elements to be diagnosed. when dlop is set high, the new data flag (ndf) field of the outgoing payload pointer in tributary tu #4 in the corresponding tug2 is
pm5361 tupp data sheet pmc-920526 issue 8 tributary unit payload processor proprietary and confidential to pmc-sierra, inc., and for its customers internal use 62 inverted, causing downstream pointer processing elements to enter a loss of pointer state. insertion of an inverted new data flag can occur in concert with the insertion of a normal idle (unequipped) indication as directed by the iidle bit. the dlop bit has no effect when the ipais bit is set high. lope: the lope bit enables loss of pointer interrupts for tributary tu #4 in the corresponding tug2. when lope is set high, an interrupt is generated upon loss of pointer and upon re-acquisition. interrupts due to lop status changes are masked when lope is set low. lopv: the lopv bit indicates the loss of pointer status of tributary tu #4 in the corresponding tug2. pf: the pf bit enables pointer follower mode for tributary tu #4 in the corresponding tug2. in pointer follower mode, the tributary fifo dead-zone is collapsed so that any variation is fifo depth will result in an outgoing pointer justification event. any tu pointer justification event on the corresponding incoming tributary, or an au pointer justification event affecting this tributary will cause an outgoing pointer justification event. config[1:0]: the config[1:0] bits are read-only and reflect the values written into the corresponding register of tu #1. the configuration specified by the config[1:0] bits are selected as follows: config[1] config[0] configuration active tu (vt) 0 0 tu2 (vt6) #1 0 1 vt3 #1, #2 1 0 tu12 (vt2) #1, #2, #3 1 1 tu11 (vt1.5) #1, #2, #3, #4
pm5361 tupp data sheet pmc-920526 issue 8 tributary unit payload processor proprietary and confidential to pmc-sierra, inc., and for its customers internal use 63 register 3fh, 5fh, 7fh: tu #4 in tug2 #1 to tug2 #7, lop interrupt bit type function default bit 7 unused x bit 6 r lop7i 0 bit 5 r lop6i 0 bit 4 r lop5i 0 bit 3 r lop4i 0 bit 2 r lop3i 0 bit 1 r lop2i 0 bit 0 r lop1i 0 this register is used to identify and acknowledge loss of pointer interrupts for the tributaries tu #4 in tug2 #1 to tug2 #7. lop1i-lop7i: the lop1i to lop7i bits identify the source of loss of pointer interrupts. in tu3 mode, these bits are unused and will return a logic 0 when read. when the corresponding tug2 tributary group is configured for tu2 (vt6), vt3, or tu12 (vt2) mode, the associated lop x i bit is unused and will return a logic 0 when read. when operational, the lop1i to lop7i bits report and acknowledge lop interrupt of tu #4 in tug2 #1 to tug2 #7, respectively. interrupts are generated upon loss of pointer and upon re-acquisition. an lop x i bit is set high when a loss of pointer event on the associated tributary occurs and are cleared immediately following a read of this register, which also acknowledges and clears the interrupt. lop x i remains valid when interrupts are not enabled (lope set low) and may be polled to detect loss of pointer events.
pm5361 tupp data sheet pmc-920526 issue 8 tributary unit payload processor proprietary and confidential to pmc-sierra, inc., and for its customers internal use 64 11 test features description simultaneously asserting (low) the csb, rdb and wrb inputs when the mbeb input is negated (low), causes all output pins and the data bus to be held in a high-impedance state. this test feature may be used for board testing. test mode registers are used to apply test vectors during production testing of the tupp. test mode registers (as opposed to normal mode registers) are selected when a[7] is high. test mode registers may also be used for board testing. when all of the tributary payload processors within the tupp are placed in test mode 0, device inputs may be read and device outputs may be forced via the microprocessor interface (refer to the section "test mode 0" for details). table 1 - test mode register memory map address register 00h-7fh normal mode registers 80h master test 81h-9fh reserved a0h tpp #1 test register 0 a1h tpp #1 test register 1 a2h tpp #1 test register 2 a3h tpp #1 test register 3 a4h-bfh reserved c0h tpp #2 test register 0 c1h tpp #2 test register 1 c2h tpp #2 test register 2 c3h tpp #2 test register 3 c4h-dfh reserved e0h tpp #3 test register 0 e1h tpp #3 test register 1
pm5361 tupp data sheet pmc-920526 issue 8 tributary unit payload processor proprietary and confidential to pmc-sierra, inc., and for its customers internal use 65 address register e2h tpp #3 test register 2 e3h tpp #3 test register 3 e4h-ffh reserved notes on test mode register bits: 1. writing values into unused register bits has no effect. however, to ensure software compatibility with future, feature-enhanced versions of the product, unused register bits must be written with logic 0. reading back unused bits can produce either a logic 1 or a logic 0; hence unused register bits should be masked off by software when read. 2. writable test mode register bits are not initialized upon reset unless otherwise noted.
pm5361 tupp data sheet pmc-920526 issue 8 tributary unit payload processor proprietary and confidential to pmc-sierra, inc., and for its customers internal use 66 register 80h: master test bit type function default bit 7 unused x bit 6 unused x bit 5 unused x bit 4 w pmctst x bit 3 w mototst x bit 2 r/w iotst 0 bit 1 w hizdata x bit 0 r/w hizio 0 this register is used to enable tupp test features. all bits, except pmctst, are reset to zero by a reset of the tupp. hizio,hizdata: the hizio and hizdata bits control the tri-state modes of the tupp . while the hizio bit is a logic 1, all output pins of the tupp except the data bus are held in a high-impedance state. the microprocessor interface is still active. while the hizdata bit is a logic 1, the data bus is also held in a high- impedance state which inhibits microprocessor read cycles. iotst: the iotst bit is used to allow normal microprocessor access to the test registers and control the test mode in each tsb block in the tupp for board level testing. when iotst is a logic 1, all blocks are held in test mode and the microprocessor may write to a block's test mode 0 registers to manipulate the outputs of the block and consequently the device outputs (refer to the "test mode 0 details" in the "test features" section). mototst: the mototst bit is used to test the decoding of the rdb_e and wrb_rwb control signals when mbeb is logic 0.
pm5361 tupp data sheet pmc-920526 issue 8 tributary unit payload processor proprietary and confidential to pmc-sierra, inc., and for its customers internal use 67 pmctst: the pmctst bit is used to configure the tupp for pmc's manufacturing tests. when pmctst is set to logic 1, the tupp microprocessor port becomes the test access port used to run the pmc "canned" manufacturing test vectors. the pmctst bit is logically "ored" with the iotst bit, and can only be cleared by setting csb to logic 1. 11.1 i/o test mode in i/o test mode, the tupp allows the logic levels on the device inputs to be read through the microprocessor interface, and allows the device outputs to be forced to either logic level through the microprocessor interface. to enable i/o test mode, the iotst bit in the master test register is set to logic 1. reading the following address locations returns the values for the indicated inputs : table 2 - i/o test mode input read register description addr bit 7 bit 6 bit 5 bit 4 bit 3 bit 2 bit 1 bit 0 h82xxxxxotmfoc1j1ospe h83 din7 din6 din5 din4 din3 din2 din1 din0 h84 x x x sclk itmf ispe ic1j1 ipar writing the following address locations forces the outputs to the value in the corresponding bit position: table 3 - i/o test mode output write register description addr bit 7 bit 6 bit 5 bit 4 bit 3 bit 2 bit 1 bit 0 h81 dout7 dout6 dout5 dout4 dout3 dout2 dout1 dout0 h82 0 0 0 0 intb otv5 otspe opar
pm5361 tupp data sheet pmc-920526 issue 8 tributary unit payload processor proprietary and confidential to pmc-sierra, inc., and for its customers internal use 68 12 operation 12.1 configuration options the tupp consists of three tributary payload processors or tpps. each tpp deals with a portion of the sonet frame that corresponds to an sts-1 spe. equivalently, each tpp deals with a portion of the sdh frame that corresponds to a vc3 together with the 2 columns of fixed stuff that are added when mapping a vc3 into an au3. by coordinating the operation of the three tpps, they can process the portion of an sdh frame that corresponds to a vc4. the coordination that may be required between the three tpps relates to the j1 byte marker and the encoding of the tributary multiframe into the h4 byte. when processing a vc4 that carries three tug3s, the alignment provided by the j1 byte marker and the h4 byte of the vc4 must be distributed to all tpps. when processing sts-1 spes, or equivalently, vc3s carried within au3s, each tpp receives its own j1 byte marker and h4 byte. coordination is accomplished as follows: the tributary multiframe alignment that is detected by tpp #1 is distributed to the two other tpps as they are not receiving h4 bytes. in addition, the input demultiplexer will stretch the pulse captured on the ic1j1 input that marks the vc4 j1 byte so that it marks the next two bytes. during the demultiplexing process this effectively feeds a "j1" marker to the two "slaved" tpps. the modes of operation of the tupp are summarized as follows: sts-1 mode this is default. each sts-1 is assumed to carry seven vt groups, each of which can be independently configured to carry vt1.5s, vt2s, vt3s, or vt6s. the ic1j1 input is expected to mark the j1 byte of each sts-1 spe and each tpp detects the tributary multiframe encoded in the unique h4 byte that it receives. au3 mode this is also the default, as is corresponds exactly to sts-1 mode, except for nomenclature. each au3 is assumed to carry seven tug2s, each of which can be independently configured to carry tu11s, tu12s, or tu2s. (the equivalent of a vt3 is allowed but there is no sdh nomenclature to describe this.) the ic1j1 input is expected to mark the j1 byte of each vc3 and each tpp detects the tributary multiframe encoded in the unique h4 byte that it receives.
pm5361 tupp data sheet pmc-920526 issue 8 tributary unit payload processor proprietary and confidential to pmc-sierra, inc., and for its customers internal use 69 au4 mode this mode is enabled when the iconcat and oconcat bits are set high. in au4 mode, individual tpps must be configured in either tug3 mode or tu3 mode. the ic1j1 input is expected to mark the j1 byte of the vc4. this j1 marker is stretched to provide a "j1" marker to each tpp. tpp #2 and tpp#3 are slaved to the tributary multiframe indication provided by tpp #1 as it is the only one that receives a valid h4 byte. tug3 mode this mode is enabled when the tug3 bit is set high in a tpp. in addition, the iconcat and oconcat bits must be set high for the tupp. the tug3 processed by the tpp is assumed to carry seven tug2s, each of which can be independently configured to carry tu11s, tu12s, or tu2s. (the equivalent of a vt3 is allowed but there is no sdh nomenclature to describe this.) when the tupp is in au4 mode, each tpp can be independently configured in tug3 or tu3 mode. tu3 mode this mode is enabled when the tu3 bit is set high in a tpp. in addition the iconcat and oconcat bits must be set high for the tupp. the tug3 processed by the tpp is assumed to carry a tu3. when the tupp is in au4 mode, each tpp can be independently configured in tug3 or tu3 mode. for figures in the operation and functional timing sections (figure 4 to figure 15), transport overhead and path overhead bytes are shown for notational convenience only. in the incoming direction, except for the h4 byte, din[7:0] does not need to contain valid transport and sts/au path overhead byte values. the h4 byte must be valid only if h4 framing is enabled (itmfen=0). otherwise, it too may be invalid. however, the incoming parity must match the data supplied at all times. in the outgoing direction, tupp places random data on dout[7:0] for transport overhead bytes. it generates all zero bytes for the sts/au path overhead except for the h4 byte which contains leading ones and an incrementing two bit pattern. the fixed stuff bytes in the tributary mapping to the synchronous payload envelope (virtual container) are also generated as all zero bytes. the outgoing parity reflects the data on dout[7:0] at all times.
pm5361 tupp data sheet pmc-920526 issue 8 tributary unit payload processor proprietary and confidential to pmc-sierra, inc., and for its customers internal use 70 12.2 sts-1 mode an example of the placement of tributaries assumed in sts-1 mode is illustrated in figure 4. for simplicity, this figure shows the frame on the dout[7:0] bus when oj1en is low. in this case the outgoing sts-1 spes are locked with respect to the outgoing transport envelope frame. this particular example assumes a snapshot of the first frame of the tributary multiframe when the v1 bytes are present. this example illustrates a vt structured sts-1 spe where all vt groups are configured to carry vt1.5s. the more general case where oj1en is high would be similar, except that the sts-1 spe would be floating within the transport envelope frame. figure 4 - sonet sts-3 carrying vt1.5 within sts-1 a1 a1 a1 a2 a2 a2 c1 c1 c1 j1 j1 j1 v1 v1 v1 spe b1 - - e1 - - f1 - - b3 b3 b3 spe spe spe spe d1 - - d2 - - d3 - - c2 c2 c2 spe spe spe spe h1 h1 h1 h2 h2 h2 h3 h3 h3 g1 g1 g1 spe spe spe spe b2 b2 b2 k1 - - k2 - - f2 f2 f2 spe spe spe spe d4 - - d5 - - d6 - - h4 h4 h4 spe spe spe spe d7 - - d8 - - d9 - - z3 z3 z3 spe spe spe spe d10 - - d11 - - d12 - - z4 z4 z4 spe spe spe spe z1 - - z2 - - e2 - - z5 z5 z5 spe spe spe spe row 1 2 3 4 5 6 7 8 9 col 123456789101112131415 270 spe spe spe spe spe spe spe spe spe spe spe spe spe spe spe spe spe spe 265 266 spe spe spe spe spe spe spe spe spe 267 spe spe spe spe spe spe spe spe spe spe spe spe spe spe spe spe spe spe 268 269 ? ? ? ? first of 3 columns occupied by vt1.5 #1 of vt group #1 of sts-1 #1 of an sts-3 stream (column set is 13, 100, 187) last of 3 columns occupied by vt1.5 #4 of vt group #7 of sts-1 #3 of an sts-3 stream (column set is 96, 183, 270) 12.3 au3 mode an example of the placement of tributaries assumed in au3 mode is illustrated in figure 5. for simplicity, this figure shows the frame on the dout[7:0] bus when oj1en is low. in this case the outgoing vc3s are locked with respect to the outgoing transport envelope frame. this particular example assumes a snapshot of the last frame of the tributary multiframe when the v4 bytes are present. this example illustrates the case where the vc3s carry tug2s and all tug2s are configured to carry tu12s. the more general case where oj1en is high would be similar, except that the vc3s would be floating within the transport envelope frame.
pm5361 tupp data sheet pmc-920526 issue 8 tributary unit payload processor proprietary and confidential to pmc-sierra, inc., and for its customers internal use 71 figure 5 - sdh stm-1 carrying tu12 within vc3/au3 a1 a1 a1 a2 a2 a2 c1 c1 c1 v4 v4 v4 spe b1 - - e1 - - f1 - - spe spe spe spe d1 - - d2 - - d3 - - spe spe spe spe h1 h1 h1 h2 h2 h2 h3 h3 h3 spe spe spe spe b2 b2 b2 k1 - - k2 - - spe spe spe spe d4 - - d5 - - d6 - - spe spe spe spe d7 - - d8 - - d9 - - spe spe spe spe d10 - - d11 - - d12 - - spe spe spe spe z1 - - z2 - - e2 - - spe spe spe spe row 1 2 3 4 5 6 7 8 9 col 123456789101112131415 270 spe spe spe spe spe spe spe spe spe spe spe spe spe spe spe spe spe spe 265 266 spe spe spe spe spe spe spe spe spe 267 spe spe spe spe spe spe spe spe spe spe spe spe spe spe spe spe spe spe 268 269 ? ? ? ? first of 4 columns occupied by tu12 #1 of tug2 #1 of vc3/ au3 #1 of an stm-1 stream (column set is 13, 76,142, 208) last of 4 columns occupied by tu12 #3 of tug2 #7 of vc3/ au3 #3 of an stm-1 stream (column set is 75, 141, 207, 270) j1 j1 j1 b3 b3 b3 c2 c2 c2 g1 g1 g1 f2 f2 f2 h4 h4 h4 z3 z3 z3 z4 z4 z4 z5 z5 z5 12.4 au4 mode an example of the placement of tributaries assumed in au4 mode is illustrated in figure 6. for simplicity, this figure shows the frame on the dout[7:0] bus when oj1en is low. in this case the outgoing vc4 is locked with respect to the outgoing transport envelope frame. this particular example assumes a snapshot of the second frame of the tributary multiframe when the v2 bytes are present. this example illustrates a case where the vc4 carries tug3s, all tug3s carry tug2s, and all tug2s are configured to carry tu12s. the more general case where oj1en is high would be similar, except that the vc4 would be floating within the transport envelope frame. figure 6 - sdh stm-1 carrying tu12 within tug3/au4 a1 a1 a1 a2 a2 a2 c1 c1 c1 - v2 v2 v2 spe b1 - - e1 - - f1 - - - spe spe spe spe d1 - - d2 - - d3 - - - spe spe spe spe h1 h1 h1 h2 h2 h2 h3 h3 h3 - spe spe spe spe b2 b2 b2 k1 - - k2 - - - spe spe spe spe d4 - - d5 - - d6 - - - spe spe spe spe d7 - - d8 - - d9 - - - spe spe spe spe d10 - - d11 - - d12 - - - spe spe spe spe z1 - - z2 - - e2 - - - spe spe spe spe row 1 2 3 4 5 6 7 8 9 col 1234567891011 192021 270 spe spe spe spe spe spe spe spe spe spe spe spe spe spe spe spe spe spe 265 266 spe spe spe spe spe spe spe spe spe 267 spe spe spe spe spe spe spe spe spe spe spe spe spe spe spe spe spe spe 268 269 ? ? ? ? first of 4 columns occupied by tu12 #1 of tug2 #1 of tug3 #1 of an stm-1 stream (column set is 19, 82, 145, 208) last of 4 columns occupied by tu12 #3 of tug2 #7 of tug3 #3 of an stm-1 stream (column set is 81, 144, 207, 270) ? ? ? ? j1 b3 c2 g1 f2 h4 z3 z4 z5 another example of the placement of tributaries assumed in au4 mode is illustrated in figure 7. for simplicity, this figure shows the frame on the
pm5361 tupp data sheet pmc-920526 issue 8 tributary unit payload processor proprietary and confidential to pmc-sierra, inc., and for its customers internal use 72 dout[7:0] bus when oj1en is low. in this case the outgoing vc4 is locked with respect to the outgoing transport envelope frame. this example illustrates the case where the vc4 carries tug3s that are all configured to carry tu3s. the more general case where oj1en is high would be similar, except that the vc4 would be floating within the transport envelope frame. figure 7 - sdh stm-1 carrying tu3 within tug3 a1 a1 a1 a2 a2 a2 c1 c1 c1 - h1 h1 h1 spe b1 - - e1 - - f1 - - - h2 h2 h2 spe d1 - - d2 - - d3 - - - h3 h3 h3 spe h1 h1 h1 h2 h2 h2 h3 h3 h3 - - - - spe b2 b2 b2 k1 - - k2 - - - - - - spe d4 --d5--d6-- - --- spe d7 --d8--d9-- - --- spe d10 - - d11 - - d12 - - - - - - spe z1 --z2--e2-- - --- spe row 1 2 3 4 5 6 7 8 9 col 1234567891011 131415 270 poh poh poh poh poh poh poh poh poh poh poh poh poh poh poh poh poh poh 16 17 poh poh poh poh poh poh poh poh poh 18 spe spe spe spe spe spe spe spe spe spe spe spe spe spe spe spe spe spe 268 269 ? ? ? ? first of 86 columns occupied by tu3 carried in tug3 #1 of an stm-1 stream last of 86 columns occupied by tu3 carried in tug3 #3 of an stm-1 stream j1 b3 c2 g1 f2 h4 z3 z4 z5 - - - - - - - - - 12 yet another example of the placement of tributaries assumed in au4 mode is illustrated in figure 8. for simplicity, this figure shows the frame on the dout[7:0] bus when oj1en is low. in this case the outgoing vc4 is locked with respect to the outgoing transport envelope frame. this particular example assumes a snapshot of the last frame of the tributary multiframe when the v4 bytes are present. this example illustrates a complex case where the vc4 carries tug3s and where tug3 #1 carries a tu3, tug3 #2 carries tug2s that are all configured to carry tu11s, and tug3 #3 carries tug2s that are all configured to carry tu12s. the more general case where oj1en is high would be similar, except that the vc4 would be floating within the transport envelope frame.
pm5361 tupp data sheet pmc-920526 issue 8 tributary unit payload processor proprietary and confidential to pmc-sierra, inc., and for its customers internal use 73 figure 8 - sdh stm-1 carrying mix of tu11, tu12, tu3 within tug3/au4 a1 a1 a1 a2 a2 a2 c1 c1 c1 - h1 h1 h1 spe b1 --e1--f1-- - h2h2h2 spe d1 - - d2 - - d3 - - - h3 h3 h3 spe h1 h1 h1 h2 h2 h2 h3 h3 h3 - - - - spe b2 b2 b2 k1 - - k2 - - - - - - spe d4 --d5--d6-- - --- spe d7 --d8--d9-- - --- spe d10 - - d11 - - d12 - - - - - - spe z1 --z2--e2-- - --- spe row 1 2 3 4 5 6 7 8 9 col 1234567891011 131415 270 poh - poh - poh - poh - poh - poh - poh - poh - poh - 16 17 - - - - - - - - - 18 spe spe spe spe spe spe spe spe spe spe spe spe spe spe spe spe spe spe 268 269 ? ? ? ? first of 86 columns occupied by tu3 carried in tug3 #1 of an stm-1 stream last of 4 columns occupied by tu12 #3 of tug2 #7 of tug3 #3 of an stm-1 stream (column set is 81, 144, 207, 270) j1 b3 c2 g1 f2 h4 z3 z4 z5 - - - - - - - - - 12 spe spe spe spe spe spe spe spe spe 19 v4 spe spe spe spe spe spe spe spe 20 v4 spe spe spe spe spe spe spe spe 21 first of 3 columns occupied by tu11 #1 of tug2 #1 of tug3 #2 of an stm-1 stream (column set is 20, 104, 188) in figure 8 above, the h1 to h3 byte in column 13 form the tu3 offset pointer. the h1 to h3 bytes in columns 14 and 15 are null pointer indications (npi) for tug3 #2 and #3.
pm5361 tupp data sheet pmc-920526 issue 8 tributary unit payload processor proprietary and confidential to pmc-sierra, inc., and for its customers internal use 74 13 functional timing the timing of the tupp input signals is illustrated in figure 9. this diagram shows a simple sts-3 case that outlines the function of the various input signals. data on din[7:0] is sampled on the rising edge of sclk. the bytes forming the three sts-1 synchronous payload envelopes are identified by the ispe signal being set high. the ic1j1 signal pulses high while ispe is low to mark the position of the first c1 byte in the sts-3 transport envelope. the ic1j1 signal is set high for three sclk periods while ispe is also set high to mark the j1 bytes of each sts-1 spe. the itmf signal is selectable to mark the v1 byte of the first tributary in an sts-1 spe or the h4 byte in the last (fourth) frame of a tributary multiframe. in this diagram, itmf is shown to be marking the last h4 byte of the tributary multiframe in sts-1 #1 and sts-1 #3. the h4 byte in sts-1 #2, as shown, is not last in the tributary multiframe. in this simple example, all sts-1 spes are aligned to the sts-3 transport envelope such that the j1 bytes directly follow the c1 bytes and no sts-1 pointer justification events are occurring. this same diagram applies for the au3 mode as it is equivalent to the sts-1 mode, except for nomenclature. figure 9 - input bus timing - simple sts-1/au3 case ic1j1 sclk ???? ispe din[7:0] a1 a1 a2 a2 a2 c1 c1 c1 a1 h2 h3 h3 h3 sts-1 #1 spe j1 byte sts-1 #2 spe j1 byte sts-1 #3 spe j1 byte no stuffing occuring h4 h4 h4 j1 j1 j1 itmf (itmfh4=1)
pm5361 tupp data sheet pmc-920526 issue 8 tributary unit payload processor proprietary and confidential to pmc-sierra, inc., and for its customers internal use 75 figure 10 shows a more complex sts-3 case that illustrates the flexibility provided by the various input signals. data on din[7:0] is sampled on the rising edge of sclk. the bytes forming the three sts-1 synchronous payload envelopes are identified by the ispe signal being set high. this example shows a negative stuff event occurring on sts-1 #2 and a positive stuff event occurring on sts-1 #3. the ic1j1 signal pulses high while ispe is low to mark the position of the c1 byte of sts-1 #1. the ic1j1 signal pulses high again to mark the j1 byte of each of the three sts-1 spes. the itmf signal is selectable to mark the v1 byte of the first tributary in an sts-1 spe or the h4 byte in the last (fourth) frame of a tributary multiframe. in this diagram, itmf is shown to be marking the v1 byte of the first tributary multiframe in sts-1 #2. the three sts- 1 spes are shown to have different alignments to the sts-3 transport envelope and the alignment is changing for two of the sts-1 spes (sts-1 #2 and #3) due to the pointer justification events shown. again, this same diagram would apply for au3 mode as it is equivalent to sts-1 mode, except for nomenclature. figure 10 - input bus timing - complex sts-1 / au3 case sclk ???? ispe ic1j1 itmf (itmfh4=0) din[7:0] a1 a1 a2 a2 a2 c1 c1 c1 a1 h1 h1 h2 h2 h2 h3 h3 h1 negative stuff byte for sts-1 #2 spe which happens to carry the j1 byte positive stuff for sts-1 #3 spe sts-1 #1 spe j1 byte j1 j1 v1 v1 byte of first tributary in sts-1 #2 v1 v1 byte of second tributary in sts-1 #2 figure 11 shows timing relationships of the various input signals in the au4 mode. data on din[7:0] is sampled on the rising edge of sclk. the bytes forming the au4 virtual container are identified by the ispe signal being set high. this example shows a negative stuff occurring for the vc4. the ic1j1 signal
pm5361 tupp data sheet pmc-920526 issue 8 tributary unit payload processor proprietary and confidential to pmc-sierra, inc., and for its customers internal use 76 pulses high while ispe is set low to mark the position of the single c1 byte in the stm-1 transport envelope. the itmf signal is selectable to mark the v1 byte of the first tributary, or the h4 byte in the last (fourth) frame of a tributary multiframe. in this diagram, itmf is shown to be marking the final h4 byte of the tributary multiframe. the ic1j1 signal pulses high to mark the single j1 byte of the vc4. this diagram applies when the tupp is in au4 mode, regardless of whether individual tributary payload processors are configured for tug3 or tu3 mode. figure 11 - input bus timing - au4 case sclk ???? ispe ic1j1 itmf (itmfh4=1) din[7:0] a1 a1 a2 a2 a2 c1 a1 h1 h1 h2 h2 h2 h1 negative stuff for vc4 which happens to carry the j1 byte h4 xx the timing of the tupp output bus is illustrated in figure 12. this diagram shows the relationships of the output signals in locked sts-1 mode. data on dout[7:0] is updated on the rising edge of sclk, and the ospe input must be logic 0. the oc1j1 signal pulses high to mark the position of the c1 byte of the first sts-1 stream in every frame of the sts-3 transport envelope. in locked sts-1 mode, the position of the j1 bytes and the sts-1 spes is implicitly defined by the c1 byte position. all three sts-1 spes are defined to be aligned to the sts-3 transport envelope such that the j1 bytes immediately follow the c1 bytes and no sts-1 pointer justification events are possible. the otmf input marks the frame containing v1 bytes. it is sampled only at the first v1 byte position of the first sts-1 stream. the bytes forming the various tributary synchronous payload envelopes are identified by the otspe signal being set high. the otv5 signal pulses high to mark the v5 bytes of each outgoing tributary.
pm5361 tupp data sheet pmc-920526 issue 8 tributary unit payload processor proprietary and confidential to pmc-sierra, inc., and for its customers internal use 77 this same diagram would apply for au3 mode as it is equivalent to sts-1 mode, except for nomenclature. figure 12 - output bus timing - locked sts-1 spes / au3 vcs case oc1j1 (oj1en=0) otmf (otmfh4=0) dout[7:0] otspe otv5 ospe sclk ???? implicit location of sts-1 spe j1 bytes a2 c1 c1 c1 h1 h1 h2 h2 h2 h3 h3 h1 h3 no stuff events possible in locked case v1 byte vt #1, sts-1 #1 v5 byte vt #1, sts-1 #2 j1 j1 j1 v1 v1 v1 v1 v1 v1 v1 v1 byte vt #1, sts-1 #2 v1 byte vt #1, sts-1 #3 v5 v1 bytes vt #2 figure 13 shows the function of the various output signals in floating sts-1 mode. data on dout[7:0] is updated on the rising edge of sclk. the bytes forming the three sts-1 synchronous payload envelopes are identified by the setting the ospe signal high. in this diagram, a negative stuff event is shown occurring on sts-1 #2 and a positive stuff event on sts-1 #3. the oc1j1 signal pulses high, while ospe is set low, to mark the c1 byte of the first sts-1 in every frame of the sts-3 transport envelope. the oc1j1 signal is set high to mark every j1 byte of each of the three sts-1 spes. the otmf input is selectable to mark the v1 byte of the first tributary in each sts-1 spe, or the h4 byte in the last (fourth) frame of a tributary multiframe. in this diagram, otmf is shown to be marking the last h4 byte of the tributary multiframe in sts-1 #1. the bytes forming the various tributary synchronous payload envelopes are identified by the otspe signal being set high. the otv5 signal pulses high to mark the v5 bytes of each outgoing tributaries. the three sts-1 spes each have different alignments to the sts-3 transport envelope and the alignment is
pm5361 tupp data sheet pmc-920526 issue 8 tributary unit payload processor proprietary and confidential to pmc-sierra, inc., and for its customers internal use 78 changing for two of the sts-1 spes (sts-1 #2 and #3) due to the pointer justification events shown. the same diagram applies for au3 mode as it is equivalent to sts-1 mode, except for nomenclature. figure 13 - output bus timing - floating sts-1 spes / au3 vcs case ???? otv5 ospe sclk oc1j1 (oj1en=1) otspe otmf (otmfh4=1) sts-1 #1 spe j1 byte dout[7:0] a1 a1 a2 a2 a2 c1 c1 c1 a1 h1 h1 h2 h2 h2 h3 h3 h1 negative stuff for sts-1 #2 spe which happens to carry a non-final h4 byte v5 byte as marked by otv5 positive stuff for sts-1 #3 spe j1 h4 vx v5 any v1 - v4 byte tu#1, sts-1 #1 last h4 byte in tributary multiframe h4 c2 the timing of the tupp output signals in locked and floating au4 modes is illustrated in figure 14 and figure 15, respectively. the operation of the various signals is analogous to the locked and floating sts-1 modes, except that there is only a single j1 byte and all pointer justification events must involve a group of three stuff bytes. these diagrams apply when the tupp is in au4 mode, regardless of whether individual tributary payload processors are configured for tug3 or tu3 mode. figure 14 shows the case of the tupp operating in locked au4 mode. data on dout[7:0] is updated on the rising edge of sclk, and the ospe input must be logic 0. the oc1j1 signal pulses high to mark the position of the single c1 byte in every frame of the au4 transport envelope. in locked au4 mode, the position of the single j1 byte and the vc4 is implicitly defined by the c1 byte position.
pm5361 tupp data sheet pmc-920526 issue 8 tributary unit payload processor proprietary and confidential to pmc-sierra, inc., and for its customers internal use 79 the vc4 is defined to be aligned to the au4 transport envelope such that the j1 byte occupies the first available payload byte after the c1 byte, and no pointer justification events are possible. the otmf input marks the frame containing v1 bytes. it is sampled only at the j1 plus one byte position of the first tug3 stream. the bytes forming the various tributary synchronous payload envelopes are identified by the otspe signal being set high. the otv5 signal pulses high to mark the v5 bytes of each outgoing tributary. figure 14 - output bus timing - locked au4 vc case sclk ???? oc1j1 (oj1en=0) otv5 ospe=0 otmf (otmfh4=0) implicit location of vc4 j1 byte dout[7:0] a2 c1 x x h4 j1 np national bytes first npi byte tug3 #1 v5 v1 v1 byte tu #1, tug2 #1, tug3 #1 last h4 byte in tributary multiframe v5 byte tu #1, tug2 #1, tug3 #1 np np npi columns otspe figure 15 shows the function of the various output signals in floating au4 mode. data on dout[7:0] is updated on the rising edge of sclk. the bytes forming the vc4 virtual container are identified by the setting the ospe signal high. the oc1j1 signal pulses high, while ospe is set low, to mark the single c1 byte in every frame of the au4 transport envelope. the oc1j1 signal is set high again with ospe high to mark the j1 byte of the vc4. the otmf input is selectable to mark the v1 byte of the first tributary in the vc4, or the h4 byte in the last (fourth) frame of a tributary multiframe. in this diagram, otmf is shown to be marking the first v1 byte. the bytes forming the various tributary synchronous
pm5361 tupp data sheet pmc-920526 issue 8 tributary unit payload processor proprietary and confidential to pmc-sierra, inc., and for its customers internal use 80 payload envelopes are identified by the otspe signal being set high. the otv5 signal pulses high to mark the v5 bytes of each outgoing tributaries. figure 15 - output bus timing - floating au4 vc case sclk ???? ospe otv5 otmf (otmfh4=0) oc1j1 (oj1en=1) dout[7:0] a1 a2 a2 a2 c1 x x v5 byte tug3 #1 national bytes v5 j1 v1 v1 v1 v1 byte tu #1, tug2 #1, tug3 #1 np np np first npi byte tug3 #1 j1 byte vc4 otspe v1 the three tributary payload processor may be individually disabled. incoming data destined to a disabled processor is re-transmitted unchanged to the outgoing data after some delay. the amount of delay is dependent on the relative phase of the incoming frame pulse (ic1j1) and the outgoing frame pulse (oc1j1). figure 16 shows the delay for the three possible alignments of ic1j1 in relation to oc1j1. the delay from the rising edge of sclk where tupp samples din[7:0] to the rising edge of sclk where a downstream device samples dout[7:0] is 5, 6, or 7 cycles.
pm5361 tupp data sheet pmc-920526 issue 8 tributary unit payload processor proprietary and confidential to pmc-sierra, inc., and for its customers internal use 81 figure 16 - by-passed mode functional timing sclk oc1j1 ic1j1 dout[7:0] a1 c1 a1 a1 a2 a2 a2 c1 c1 din[7:0] c1 c1 c1 a2 sclk oc1j1 ic1j1 dout[7:0] a1 c1 a1 a1 a2 a2 a2 c1 c1 din[7:0] c1 c1 c1 a2 sclk oc1j1 ic1j1 dout[7:0] a1 c1 a1 a1 a2 a2 a2 c1 c1 din[7:0] c1 c1 c1 a2 5 byte delay 6 byte delay 7 byte delay
pm5361 tupp data sheet pmc-920526 issue 8 tributary unit payload processor proprietary and confidential to pmc-sierra, inc., and for its customers internal use 82 14 absolute maximum ratings ambient temperature under bias -40c to +85c storage temperature -40c to +125c supply voltage -0.5v to +6.0v voltage on any pin -0.5v to v dd +0.5v static discharge voltage 500 v latch-up current 100 ma dc input current 20 ma lead temperature +230c absolute maximum junction temperature +150c
pm5361 tupp data sheet pmc-920526 issue 8 tributary unit payload processor proprietary and confidential to pmc-sierra, inc., and for its customers internal use 83 15 d.c. characteristics (t a = -40c to +85c, v dd = 5 v 10%) table 4 - d.c. characteristics symbol parameter min max units conditions v il input low voltage -0.5 0.8 volts guaranteed input low voltage v ih input high voltage 2.0 v dd +0.5 volts guaranteed input high voltage v ol output or bidirectional low voltage 0.4 volts v dd = min, i ol = 4 ma, note 3 v oh output or bidirectional high voltage 2.4 volts v dd = min, i oh = 4 ma, note 3 v t+ reset input high voltage 3.5 volts v t- reset input low voltage 1.0 volts v th reset input hysteresis voltage volts typically 0.65v i ilpu input low current +20 +20 0 a v il = gnd, notes 1, 3 i ihpu input high current -10 0 a v ih = v dd , notes 1, 3 i ilpd input low current 0 +10 a v il = gnd, notes 4, 3 i ihpd input high current -200 -20 a v ih = v dd , notes 4, 3 i il input low current 0 +10 a v il = gnd, notes 2, 3
pm5361 tupp data sheet pmc-920526 issue 8 tributary unit payload processor proprietary and confidential to pmc-sierra, inc., and for its customers internal use 84 symbol parameter min max units conditions i ih input high current -10 0 a v ih = v dd , notes 2, 3 c in input capacitance 5 pf excluding package, package typically 2 pf c out output capacitance 5 pf excluding package, package typically 2 pf c io bidirectional capacitance 5 pf excluding package, package typically 2 pf i ddop1 operating current processing tributaries 180 ma v dd = 5.5 v, outputs unloaded, sclk = 19.44 mhz, alternating data, processing tributaries i ddop2 operating current tributary processors bypassed 60 ma v dd = 5.5 v, outputs unloaded, sclk = 19.44 mhz, alternating data, tributary processors bypassed i ddsb standby current 100 ua v dd = 5.5 v, outputs unloaded, no clocks notes on d.c. characteristics: 1. input pin or bidirectional pin with internal pull-up resistor. 2. input pin or bidirectional pin without internal pull-up resistor 3. negative currents flow into the device (sinking), positive currents flow out of the device (sourcing). 4. input pin or bidirectional pin with internal pull-down resistor.
pm5361 tupp data sheet pmc-920526 issue 8 tributary unit payload processor proprietary and confidential to pmc-sierra, inc., and for its customers internal use 85 16 microprocessor interface timing characteristics (t a = -40c to +85c, v dd = 5 v 10%) table 5 - microprocessor interface read access (figure 17, figure 18) symbol parameter min max units ts ar address to valid read set-up time 25 ns th ar address to valid read hold time 20 ns ts rwb rwb to valid read set-up time 25 ns th rwb rwb to valid read hold time 20 ns ts alr address to latch set-up time 20 ns th alr address to latch hold time 20 ns tv l valid latch pulse width 20 ns ts lr latch to read set-up 0 ns th lr latch to read hold 20 ns tp rd valid read to valid data propagation delay 80 ns tz rd valid read negated to output tri-state 20 ns tz inth valid read negated to output tri-state 50 ns
pm5361 tupp data sheet pmc-920526 issue 8 tributary unit payload processor proprietary and confidential to pmc-sierra, inc., and for its customers internal use 86 figure 17 - microprocessor interface read timing (intel mode) intb tz inth (csb+rdb) valid data d[7:0] tp rd tz rd ts ar th ar valid address a[7:0] ale ts alr tv l ts lr th alr th lr
pm5361 tupp data sheet pmc-920526 issue 8 tributary unit payload processor proprietary and confidential to pmc-sierra, inc., and for its customers internal use 87 figure 18 - microprocessor interface read timing (motorola mode) intb tz int (!csb & e) valid data d[7:0] tp rd tz rd valid address a[7:0] ale ts alr tv l ts lr th alr th lr th ar rwb ts rwb th rwb ts ar
pm5361 tupp data sheet pmc-920526 issue 8 tributary unit payload processor proprietary and confidential to pmc-sierra, inc., and for its customers internal use 88 notes on microprocessor interface read timing: 1. output propagation delay time is the time in nanoseconds from the 1.4 volt point of the reference signal to the 1.4 volt point of the output. 2. maximum output propagation delays are measured with a 100 pf load on the microprocessor interface data bus, (d[7:0]). 3. a. in intel mode, a valid read enable bar is defined as a logical or of the csb and the rdb signals. b. in motorola mode, a valid read enable is defined as a logical and of the e signal, the rwb signal, and the inverted csb signal. 4. microprocessor interface timing applies to normal mode register accesses only. 5. in non-multiplexed address/data bus architectures, ale should be held high, parameters ts alr , th alr , tv l , and ts lr are not applicable. 6. parameters th ar and ts ar are not applicable if address latching is used. 7. when a set-up time is specified between an input and a clock, the set-up time is the time in nanoseconds from the 1.4 volt point of the input to the 1.4 volt point of the clock. 8. when a hold time is specified between an input and a clock, the hold time is the time in nanoseconds from the 1.4 volt point of the clock to the 1.4 volt point of the input. table 6 - microprocessor interface write access (figure 19, figure 20) symbol parameter min max units ts aw address to valid write set-up time 25 ns ts dw data to valid write set-up time 20 ns ts alw address to latch set-up time 20 ns th alw address to latch hold time 20 ns tv l valid latch pulse width 20 ns
pm5361 tupp data sheet pmc-920526 issue 8 tributary unit payload processor proprietary and confidential to pmc-sierra, inc., and for its customers internal use 89 symbol parameter min max units ts lw latch to write set-up 0 ns th lw latch to write hold 20 ns th dw data to valid write hold time 20 ns th aw address to valid write hold time 20 ns tv wr valid write pulse width 40 ns ts rwb rwb to write set-up time 25 ns th lw rwb to write hold time 20 ns figure 19 - microprocessor interface write timing (intel mode) th dw valid data d[7:0] tv wr ts aw th aw ts dw (csb+wrb) a[7:0] valid address ale tv l ts alw ts lw th alw th lw
pm5361 tupp data sheet pmc-920526 issue 8 tributary unit payload processor proprietary and confidential to pmc-sierra, inc., and for its customers internal use 90 figure 20 - microprocessor interface write timing (motorola mode) tv wr (!csb & e) a[7:0] valid address th dw valid data d[7:0] ts dw ale tv l ts alw ts lw th alw th lw th aw ts aw rwb ts rwb th rwb notes on microprocessor interface write timing: 1. a. in intel mode, a valid write strobe bar is defined as a logical or of the csb and the wrb signals. b. in motorola mode, a valid write strobe is defined as a logical and of the e signal, the inverted rwb signal, and the inverted csb signal. 2. microprocessor interface timing applies to normal mode register accesses only.
pm5361 tupp data sheet pmc-920526 issue 8 tributary unit payload processor proprietary and confidential to pmc-sierra, inc., and for its customers internal use 91 3. in non-multiplexed address/data bus architectures, ale should be held high, parameters ts alw , th alw , tv l , and ts lw are not applicable. 4. parameters th aw and ts aw are not applicable if address latching is used. 5. output propagation delay time is the time in nanoseconds from the 1.4 volt point of the reference signal to the 1.4 volt point of the output. 6. when a set-up time is specified between an input and a clock, the set-up time is the time in nanoseconds from the 1.4 volt point of the input to the 1.4 volt point of the clock. 7. when a hold time is specified between an input and a clock, the hold time is the time in nanoseconds from the 1.4 volt point of the clock to the 1.4 volt point of the input.
pm5361 tupp data sheet pmc-920526 issue 8 tributary unit payload processor proprietary and confidential to pmc-sierra, inc., and for its customers internal use 92 17 tupp timing characteristics (t a = -40c to +85c, v dd = 5 v 10%) table 7 - tupp input (figure 21) symbol description min max units sclk frequency (nominally 19.44 mhz ) 20 mhz sclk duty cycle 40 60 % ts din din set-up time 5 ns th din din hold time 3 ns ts ipar ipar set-up time 5 ns th ipar ipar hold time 3 ns ts spe ispe and ospe set-up time 5 ns th spe ispe and ospe hold time 3 ns ts c1j1 ic1j1 and oc1j1 set-up time 5 ns th c1j1 ic1j1 and oc1j1 hold time 3 ns ts tmf itmf and otmf set-up time 5 ns th tmf itmf and otmf hold time 3 ns
pm5361 tupp data sheet pmc-920526 issue 8 tributary unit payload processor proprietary and confidential to pmc-sierra, inc., and for its customers internal use 93 figure 21 - input timing ts din th din din[7:0] ts spe th spe ispe/ ospe sclk ts c1j1 th c1j1 ic1j1/ oc1j1 ts tmf th tmf itmf/ otmf ts ipar th ipar ipar notes on input timing: 1. when a set-up time is specified between an input and a clock, the set-up time is the time in nanoseconds from the 1.4 volt point of the input to the 1.4 volt point of the clock.
pm5361 tupp data sheet pmc-920526 issue 8 tributary unit payload processor proprietary and confidential to pmc-sierra, inc., and for its customers internal use 94 2. when a hold time is specified between an input and a clock, the hold time is the time in nanoseconds from the 1.4 volt point of the clock to the 1.4 volt point of the input. table 8 - tupp output (figure 22) symbol description min max units tpdout sclk high to dout valid propagation delay 3 25 ns tpopar sclk high to dout valid propagation delay 3 25 ns tptspe sclk high to otspe valid propagation delay 3 25 ns tptv5 sclk high to otv5 valid propagation delay 3 25 ns figure 22 - output timing tp dout dout[7:0] tp tspe otspe tp tv5 otv5 sclk tp opar opar
pm5361 tupp data sheet pmc-920526 issue 8 tributary unit payload processor proprietary and confidential to pmc-sierra, inc., and for its customers internal use 95 notes on output timing: 1. output propagation delay time is the time in nanoseconds from the 1.4 volt point of the reference signal to the 1.4 volt point of the output. 2. maximum output propagation delays are measured with a 50 pf load on the outputs.
pm5361 tupp data sheet pmc-920526 issue 8 tributary unit payload processor proprietary and confidential to pmc-sierra, inc., and for its customers internal use 96 18 ordering and thermal information table 9 - tupp ordering information part no. description PM5361-RI 160 copper leadframe plastic quad flat pack (pqfp) pm5361-ei 160 plastic quad flat pack (pqfp) with fused corner pins table 10 - tupp thermal information part no. ambient temperature theta ja theta jc PM5361-RI -40c to 85c 45 c/w 13 c/w pm5361-ei -40c to 85c 31 c/w 10 c/w
pm5361 tupp data sheet pmc-920526 issue 8 tributary unit payload processor proprietary and confidential to pmc-sierra, inc., and for its customers internal use 97 19 mechanical information e d d1 1 designator pin 1 e1 e 160 0.65 0.10 0.38 0.22 1.03 0.88 body size: ccc b e l e1 e d1 d a2 a1 a dim. max. min. nom. package type: 160 pin metric plastic quad flatpack-mqfp 3.42 4.07 0.25 0.39 3.17 3.42 30.95 31.20 31.45 27.85 28.00 28.10 30.95 31.20 31.45 27.85 28.00 28.10 0.73 8-12 deg a 8-12 deg a2 see detail a 3.68 28 x 28 x 3.49 mm gage plane, 0.25 above seating plane. detail a 0-7 deg plane seating 0.13-0.23 c l .25 a 0-10 deg. ccc c lead coplanarity notes: 1) all dimensions in millimeter. b standoff a1 3) foot length "l" is measured at c with tolerances as indicated. 2) dimensions shown are nominal
pm5361 tupp data sheet pmc-920526 issue 8 tributary unit payload processor proprietary and confidential to pmc-sierra, inc., and for its customers internal use 98 notes
pm5361 tupp data sheet pmc-920526 issue 8 tributary unit payload processor proprietary and confidential to pmc-sierra, inc., and for its customers internal use 99 notes
pm5361 tupp data sheet pmc-920526 issue 8 tributary unit payload processor none of the information contained in this document constitutes an express or implied warranty by pmc-sierra, inc. as to the suf ficiency, fitness or suitability for a particular purpose of any such information or the fitness, or suitability for a particular purpose, merchanta bility, performance, compatibility with other parts or systems, of any of the products of pmc-sierra, inc., or any portion thereof, referred to in this document. pmc-sierra, inc. expressly disclaims all representations and warranties of any kind regarding the contents or use of the information, including, but not l imited to, express and implied warranties of accuracy, completeness, merchantability, fitness for a particular use, or non-infringement. in no event will pmc-sierra, inc. be liable for any direct, indirect, special, incidental or consequential damages, including, but not limited to, lost profits, lost business or lost data resulting from any use of or reliance upon the information, whether or not pmc-sierra, inc. has been advised of the possibility of such damage. ? 1998 pmc-sierra, inc. pmc-920526 (r8) ref pmc-920102 (r10) issue date: july 1998 proprietary and confidential to pmc-sierra, inc., and for its customers internal use contacting pmc-sierra, inc. pmc-sierra, inc. 105-8555 baxter place burnaby, bc canada v5a 4v7 tel: (604) 415-6000 fax: (604) 415-6200 document information: document@pmc-sierra.com corporate information: info@pmc-sierra.com application information: apps@pmc-sierra.com (604) 415-4533 web site: http://www.pmc-sierra.com

▲Up To Search▲

Price & Availability of PM5361-RI

	To Download PM5361-RI Datasheet File
If you can't view the Datasheet, Please click here to try to view without PDF Reader .